Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I hear you!

    Think about what happens when the perl version is increased by a minor version (i.e. 5.8.7 -> 5.8.8).

    Steffen
  • This caused quite the shit storm with the Ruby community as well. Having to deal with, "Why does my require fail" on IRC almost every day is reason enough to have the Debian package managers beaten with a rubber hose.

    As far as I can tell Debian is run by a bunch of twenty-somethings who think they're experts on package management, and they're going to save us 5 MB of disk space, whether we want them to or not. I know I'll never use a Debian flavored distro.

  • Debian's package management system is a thing of beauty. It works far better than anything else I've had to use (e.g. Red Hat). However for packages that you work directly with that have many components - like Perl, things can sometimes go a little odd. You must either use only packaged components or install your own version in /usr/local and managed that manually (e.g. with CPAN). Mixing CPAN and the distro packaged version of Perl isn't always safe...

    --
    -- "It's not magic, it's work..."
  • I think it's pretty simple: modules provided by debian go in /usr manually installed modules go in /usr/local This works great if you stick to a stable release since the perl version won't be changing. Obviously it's not as convenient if you are using something other than stable. Of course, you're going to be stuck with the debian provided versions, and they have long release cycles, but IMHO I think that's a small price to pay compared to performing system/security updates.