Re: The better way to update/write new CPAN Apache modules

[prev] [thread] [next] [Date index for 2005/05/12]

From: J Matisse Enzer
Subject: Re: The better way to update/write new CPAN Apache modules
Date: 18:50 on 12 May 2005
On May 12, 2005, at 7:22 AM, Enrico Sorcinelli wrote:

> I am using mod_perl2 from almost 2 years but there are a lot of users 
> that still
> use mod_perl 1 and/or mod_perl 2 prior to RC5, so for my Apache CPAN 
> modules I
> would like to continue to support all versions with the minimum effort 
> (of
> course :-)) by avoiding duplications of docs, code and so on.

For what it's worth, I have decided that for the Apache::AuthCookieDBI 
module (which I maintain) that all new releases will be in the 
Apache2::** namespace.

My personal (not very strong) opinion is that all mod_perl 2.x modules 
should be in CPAN under Apache2::*, to avoid confusion. The README and 
INSTALL and perldoc can (and should) mention any Apache::* versions.

-Matisse

-------------------------------------------------------
Matisse Enzer <matisse@xxxxxxx.xxx>
http://www.matisse.net/  - http://www.eigenstate.net/

The better way to update/write new CPAN Apache modules
Enrico Sorcinelli 14:22 on 12 May 2005

Re: The better way to update/write new CPAN Apache modules
Philip M. Gollucci 18:05 on 12 May 2005

Re: The better way to update/write new CPAN Apache modules
J Matisse Enzer 18:50 on 12 May 2005

Generated at 06:57 on 17 May 2005 by mariachi v0.52