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.
  • Irrelevant (Score:2, Interesting)

    The maintainers of perl for various platforms seem to all have failed to have working installations of perl anyways. At least I cannot remeber when I last used a system installed perl for anything I did or installed. It would all just break break break with things installed of CPAN.

    Frankly, it is just silly hair splitting.

    • Re:Working Perl (Score:2, Insightful)

      Package management systems like dpkg and rpm simply don't cooperate with CPAN. They need to know what files are installed and what packages installed them, and CPAN installations are far too undisciplined to report what's been installed and where (and, even more important in some ways, what's been removed). And then there are the dependency tracking issues.

      In short, if you use rpm or dpkg, you shouldn't be using CPAN in the first place. This has nothing to do with the skill or dedication of the package

      • Certainly in Debian, a few CPAN modules are packaged as libfoo-perl. There has been talk IIRC of a Debian-specific version of or something similar which will inform apt (probably by wrapping the equivs package) when new perl modules are installed or upgraded by CPAN.

        It would in theory be possible to "automatically" convert every module on CPAN to a Debian module. Perhaps we need to set up as some kind of automagic gateway ;)