3 ms·
> But installing one was the big issue, as it would always choose the latest release of any module in the dependency chain, including the perl interpreter itsel
by ether_at_cpan 7y ago
> But installing one was the big issue, as it would always choose the latest release of any module in the dependency chain, including the perl interpreter itself.
You are mistaken. No cpan client is capable of upgrading perl itself. If a cpan module declares a dependency on a perl version later than what you are currently running, the installation simply fails (as what would happen if there is a dependency declaration on a module that is shipped with core and is not upgradable separately, e.g. 'strict' or 'POSIX').
- gmiller123456 7y agoMaybe that's how it is today, but every time I installed a module in would invariably end with CPAN downloading the source of the latest build, compile it, and install it. Then I'd have to go and re-install every module under the new version.
- Grinnz 7y agoWell, not strictly mistaken, but severely outdated. The CPAN module did try to upgrade Perl in ancient versions, and this of course was a terrible idea.
- peteretep 7y agoThis is true now, but was not true many years ago.
- Grinnz 7y agoTo put some numbers in this thread, it was fixed in CPAN.pm version 1.90 in 2007, which first came with Perls 5.8.9 and 5.10.0 (but can be updated on older Perls).