Debian Lenny libapache2-mod-perl2 package description incorrectly lists the module name of "Apache::Registry"

[Imran Chaudhry]

On Tue, 2009-04-21 at 08:55 -0400, Jonathan Yu wrote:
> Hi Imran:
> 
> Thanks for the bug report.

Hi Johnathan, thanks for the reply.

I have made a few similar bug reports recently but this is the first
time I have had a reply from someone.


> > I favour allowing both names if possible (some sort of aliasing?)
> Both names would not be a good idea. First of all, the reason why
> different namespaces were used in the first place is that
> Apache::Registry is (to my knowledge) not compatible with
> ModPerl::Registry.

Fair enough. For some context, I am currently upgrading a mod-perl web
app from Apache1 to Apache2. It's not using mod-perl in any
sophisticated way, however I used ModPerl::Registry in my vhost like
this and a cursory test appeared to work perfectly:

	<Directory /var/www/x3/cgi-bin>
		AllowOverride AuthConfig
		Options +ExecCGI +Includes -Multiviews
		Order allow,deny
		Allow from all
		SetHandler perl-script
		#PerlHandler Apache::Registry
		PerlHandler ModPerl::Registry
	</Directory>


> What we can perhaps look into doing is providing a stub module which
> would act as an alias for Apache::Registry and state that
> ModPerl::Registry should be used instead. However, I'm not sure of the
> real-world use of this, because every modperl2 based tutorial will
> mention ModPerl::Registry and not the former.

I wouldn't bother then :)

> Thanks for the bug report and I hope this helps.

Yep, thanks!

Regards

Imran Chaudhry
Software Engineer

SmoothWall Ltd
1 John Charles Way
Leeds
LS12 6QA

Tel: +44 (0)870 1 999 500
Fax: +44 (0)870 1 991 399

SmoothWall Ltd. - http://www.smoothwall.net/

This email and any attachments transmitted with it are confidential to
the
intended recipient(s) and may not be communicated to any other person or
published by any means without the express permission of SmoothWall
Limited.

Any views expressed in this message are solely those of the author.

See: http://www.smoothwall.net/emailnotice.html for the full text of
this notice.