I'm running a perl -MCPAN -e 'CPAN::Shell->install(CPAN::Shell->r)', to see if it helps me with a PerlMagick/ImageMagick version(?) incompatibility, and in the process, it decided to upgrade my mod_perl...
to 1.29.
As Stas knows, I've actually already installed 1.99 for Apache2, and I'm wondering if CPAN's likely to have broken anything for me. I suspect not, I'm just tying up loose ends.
Oh, and will in-place upgrading my perl from 5.6.1 to 5.8.1 break things? Will I, for example, have to rebuild mod_perl or anything?
Assuming that any 3rd party mp2 modules are written to use ModPerl::MM, they will all install themselves into Apache2/ subdirs. mp1 3rd party modules will go to the normal places. The only problem with 3rd party mp2 modules is that CPAN.pm won't be able to find them, unless you adjust @INC and it'll try to install modules even though there are already installed. Therefore what you want to do when working with CPAN.pm is:
# to install/update mp1 modules perl -MCPAN -eshell
# to install/update mp2 modules perl -MCPAN -MApache2 -eshell
and you can't use the cpan script for starting CPAN.pm shell to update mp2 modules, unless you start it with:
perl -MApache2 /path/to/cpan
or you make a copy of it, e.g. cpan-mp2 and you add 'use Apache2' at the very beginning of it. Again, if you use the normal cpan script it won't have any idea that you have some modules installed already, and will try to install them again.
This trick needs to make it to the docs...
I don't use CPANPLUS, so if someone can write the parallel instructions for invokind the CPANPLUS shell, it'd be very helpful.
__________________________________________________________________ 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
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
