Stas Bekman <[EMAIL PROTECTED]> writes: > Joe Schaefer wrote:
[...] >> Looks very promising to me. Is there a way to tell PAUSE to index >> mod_perl's Apache::* modules from a bundle? If so, that might >> provide a decent solution for both mod_perl and libapreq >> (and other Apache::* modules that find themselves in a similar situation). > > I'm not sure I understand what you ask, Joe. The indexer indexes > anything that upload to PAUSE (as long as you have perms). > > So we need release mp1 with a new package: > > Bundle::mod_perl1::core > > which has the same version as mod_perl.pm > > and mp2 distro with: > > Bundle::mod_perl2.0::core > > which has the same version as mod_perl.pm > > Now other packages can create a dependency on those packages, instead of > mod_perl.pm. If you're going that route, I really see that as being worse than introducing a new mod_perl2 package with mp2 and restoring all of mp1's CPAN indexing (including mod_perl.pm). I now think was a mistake for any of the Apache::* core modules to be indexed with mp1, because it looks like a wedding between the Apache:: APIs and the mp1 implementation of them. This is, IMO, the kernel of the complaints against the mp2 release plan. -- Joe Schaefer -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
