On Tue, Oct 21, 2003 at 09:55:59AM -0700, Stas Bekman wrote:
Leon has kindly forwarded to me Autrijus' notes from the last CPAN meeting which unfortunately I couldn't attend:
http://cplan.kwiki.org/?MinutesAccordingToAutrijus
and the information about this new list.
I'm most interested in the outcome of the two topics: 'Group Authors' and 'Modules with several versions on CPAN'.
1. Group Authors
* PAUSE has existing mechanism to use mailing lists as author keys * The goal is for it to stay consistent across maintainers * Groups should get their own directories * Maybe groups/id/P5P in addition to authors/id/F/FO/FOOBAR?
I don't think there's any need for a different directory structure. Groups share the same namespace as authors so can live with them.
The four items above were copy-n-pasted from http://cplan.kwiki.org/?MinutesAccordingToAutrijus, I didn't come up with them ;)
Sounds very promising. What are the plans for implementation this.
Mainly in Andreas' hands I guess.
OK, now I know whom to nudge ;) Andreas, do you need a guinea pig?
I'm willing to help test things. We could use Apache-Test for this purpose which is maintained by Doug MacEachearn, me and Geoffrey Young at the moment, but more maintainers may join later.
2. 'Modules with several versions on CPAN'.
I couldn't find this issue resolved/discussed in the notes.
What's going to happen when mod_perl 2.0 is released on CPAN? All users will then get mod_perl 2.0 fetched even if they want mod_perl 1.0. mod_perl 2.0 doesn't replace mod_perl 1.0, so using the-latest-version-is-the-one-you-want approach doesn't work here. Have you discussed this issue?
All I recall was that the dependency metadata needs to be able to handle more complex expressions than at present in order to prevent incompatible future versions of future modules
Cool. But are there any concrete plans to implement those more complex expressions? ;)
And then authors would still have to actually add eg "mod_perl < 2" to the dependency list of modules that don't support mod_perl 2.
Yeah, but how do you tell CPAN/CPANPLUS clients that via the PREREQ_PM list?
And how do they handle that interactively, when users say:
cpan> install mod_perl
?
Personally I'd suggest renaming "mod_perl" version 2 to "mod_perl2" and so completely duck the issue for now. I doubt it could get fixed in time for you.
If it was only one module, than we could consider that. But there are many, and renaming them is a bad idea, since users will have to modify their code and make it conditional, even though those modules haven't changed their user API. e.g. If you have use Apache::Request in your project, it'll work exactly the same under mp1 and mp2. why changing the name? the only problem is how the program (dependency list) or the user (interactive) get to tell CPAN that they want a specific generation.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
