The better way to update/write new CPAN Apache modules

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

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