The better way to update/write new CPAN Apache modules

[Enrico Sorcinelli <be...@perl.it>]

Hi all,

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.

So there are at least three possibilities:

1. One module (single CPAN distribution) that supports all mp* versions (with
inline API run-time tests) into Apache::* namespace;

2. Two modules (single CPAN distribution, Apache::* _or_ Apache2::* ?):
- one for mp1 + mp2 < RC5 into Apache::* namespace; (with inline API run-time
tests)
- one for mp2 >= RC5 only into Apache2::* namespace (with no tests)

3. Two modules into two different CPAN distributions (Apache::* _and_
Apache2::*). This is the same case of 2) with the difference that there are 2
distributions and maybe a little bit of extra maintenance.

Moreover, for new Apache modules, is the Apache2:** namespace the
standard/suggested choice?

Any suggestions and/or comments?

Sorry in advance if this topic has been already discussed (probably), however I
haven't found the final response for my (little) doubts :-)


	- Enrico 

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

[J Matisse Enzer <ma...@matisse.net>]

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 <ma...@matisse.net>
http://www.matisse.net/  - http://www.eigenstate.net/

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

["Philip M. Gollucci" <pg...@p6m7g8.com>]

Enrico Sorcinelli wrote:

>2. Two modules (single CPAN distribution, Apache::* _or_ Apache2::* ?):
>- one for mp1 + mp2 < RC5 into Apache::* namespace; (with inline API run-time
>tests)
>- one for mp2 >= RC5 only into Apache2::* namespace (with no tests)
>  
>
Our general practice is that you should _NOT_ support mp2 < RC5 at this 
point only
mp1 and mp2 RC5+

I don't believe there's been a statement about Apache2::* but it seems 
to be the way things are going
if you do decide to split them.


-- 
END
-----------------------------------------------------------------------------
Philip M. Gollucci
Senior Developer - Liquidity Services Inc.
Phone:  202.558.6268 (Direct)
E-Mail: pgollucci@liquidation.com
Web:    http://www.liquidation.com