Andrew Hewus Fresh <and...@afresh1.com> wrote: > This would do it, you will need to update this file that you've someone > installed manually, this covers over the one that ships with base and > will definitely cause that issue. Removing the files installed by the > old version of perl's cpan client should get things working again though.
It is completely ridiculous that base perl is affected by something which lands in /usr/local It is absolutely unacceptable. > I will try to think about how we could put the pkg installed modules in > the current dir and the cpan installed files into a versioned dir. Not > sure quite how to do that without bumping every perl module, but I'll > think about it more. That seems entirely backwards. You want to crank base perl over and over and over when the outside universe changes? That will make all the perl upgrade tools even *LESS* reliable
