The best option would be to package CPAN and also include a default configuration for it that avoids it trampling on distro managed directories, e.g. use /usr/local/CPAN for all CPAN-installed (or upgraded) packages, and a suitable Perl library path so that everything uses this tree first. Then the Perl user can use CPAN and know that anything installed by CPAN takes priority over the version in the distro, while still being able to upgrade the distro's Perl-based packages.
What would be even nicer is a simple tool that, given a CPAN package name, first tries the distro's packaged versions of CPAN packages, and only if they don't exist tries CPAN directly.
Posted Aug 28, 2009 15:41 UTC (Fri) by epa (subscriber, #39769)
[Link]
...better still, first tries the distro's own repository, then attempts to
get the package from CPAN and build a package of it using a tool like
cpanflute2, cpan2rpm, makerpm.pl, etc etc.