Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I'm astonished to see that a lot of people using Linux are still using the cpan shell to install modules. Today, all respectable Linux distributions have a packaging system. When a module is available in the packaging system it should be used. This provides the best and easiest way for installing it and its dependencies.

    When a module in the repository is missing or is to old all that's needed is to package it and to add it to a personal repository. Debian makes this very easy thanks to dh-make-perl and to

    • I agree with your basic premise, but the great thing about CPAN is that it's there when you need it. It's a lowest common denominator that you can fallback on when you're on an unfamiliar system, or one that doesn't provide a decent system for packaging perl modules (for example, Windows or OS X).

      • I also agree with you. This is why I specified in the comment that my opinion regards mostly Linux. As far as I know Windows and OS X have no "official" packaging mechanism. Under these OSes CPAN shell is more than a welcomed tool since installing modules would be nightmare without it.

        Also the CPAN shell has many more features and usages than to install modules. The tool is needed and useful. What I deplore is that it is used all the time to install Perl modules. As Jozef exposed, this has some serious impl