kjeldahl writes "I've been using "perl -MCPAN -e shell" to auto install a lot of perl stuff that some of my software use. It used to be so easy; flip that CD onto the machine, load up the OS (usually RedHat or Mandrake) and have perl CPAN fix the rest. This used to work so well. Now it does not any longer. For some reason, sometimes when I install some perl module (very often MLDBM, but I am not sure) CPAN decides I need to upgrade perl 5.6.1. If I stop it and install using (inside the CPAN shell) "look MLDBM", and the usual perl Makefile.pl;make;make test;make install everything seems to build and work fine. At least until I hit another perl module that try to do me a favour by upgrading to 5.6.1.
It is not that I do not want to upgrade. However, for a lot of machines it is simply not worth the effort. I do not want to recompile the web server and do the mod_perl and ssl stuff manually; I just want to install the stuff on one of my development laptops.
So, to summarize: Can this behaviour be turned off? Is there any reason why it _insists_ on installing 5.6.1 when I do not want it to? Is there any MAJOR flaw in 5.6.0 that make it unusable?"
This problem never seems to go away, and I don't know the solution.
My procedure for doing this:
perl -MCPAN -e shell
install CPAN
install Bundle::CPAN
install Whatever::Module
Doing the install CPAN as opposed to the install Bundle::CPAN might seem counterintuitive but it ensures that you don't pull in any of the dependencies before pulling in the newest CPAN version, which usually takes care of the perl upgrade issue.
Chris
