I have also been hit by this problem on a Debian upgrade from Etch (perl-modules v5.8.8-7etch7) to Lenny (perl-modules v5.10.0-19lenny2).
I accept the comments above regarding not using the system perl are valid in terms of keep tight control of an application environment.
However that said I feel that the upgrade from perl v5.8 to v5.10 should still be handled differently. For one it deleted my /usr/local/share/perl/5.8.8 directory structure which had been built by me installing modules using "perl -MCPAN -e shell". Given that none of the Debian perl packages populated /usr/local/share/perl/5.8.8 I feel hard done by that the upgrade deleted them.
In addition the perl upgrade could display a notification of this situation. It could go further and even pull in new CPAN modules automatically to match. That might be too much to automate, but I do feel that it could do more to assist the person doing the upgrade.
All the best,
Cheers,
Mark
In reply to Re: When you change Perl versions, how do you resync all the CPAN modules you have installed [tag://sysadmin,cpan,modules,upgrade]
by marky1124
in thread When you change Perl versions, how do you resync all the CPAN modules you have installed [tag://sysadmin,cpan,modules,upgrade]
by metaperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |