Randal L. Schwartz wrote:
Whomever is maintaining Apache::Resource needs to release a version to
the CPAN greater than 1.72 that is *not* inside the mod_perl2 distro,
because it's apparently also bundled inside the mod_perl2 distro, and
this is a pain for those of us who do not wish to upgrade to mod_perl2
just yet.

This is the same problem as when other formerly CPAN modules get
incorporated into a later Perl distro.

Please either unincorporate it (and then cpan-delete 2.0.0-RC1),
or release a separate version of it as well.

Sorry Randal, but this is a PAUSE+CPAN/CPANPLUS problem, not ours. I've spent a lot of time in the last 3 years warning about the problem, trying to push for a solution sending various proposals, but nothing was done.


Apache::Resource lives in mod_perl-1.x and mod_perl-2.x, and so do many other modules with the same names. So this is not a problem of Apache::Resource only.

This problem is different from perl-core + CPAN dual-life modules you are talking about. This problem is about foo-core-gen-1 + foo-core-gen-2 + ... + foo-core-gen-N. This is a problem we have all seen with GD and a few other modules, when the same module name suddenly was requiring a different underlying environment (libgd in the case of GD). Noone cares to fix it so now a lot of people going to find this problem with mod_perl2 being indexed by PAUSE.

If you are interested I can dig up the references to threads where those issues were discussed (mainly p5p) and feel free to push it for a solution. I've given up talking to walls.

--
__________________________________________________________________
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



Reply via email to