Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
------------------------------------------------------------------
Meanwhile I've found a solution proposed by Andreas 1.5 years ago, which
might work as a better workaround from all the ones proposed so far: http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-05/msg00264.html
------------------------------------------------------------------
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.
The question is whether we should tell PAUSE to exclude any other packages from indexing.
-- __________________________________________________________________ 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
-- 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