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

use Perl Log In

Log In

[ Create a new account ]

phillup (4419)

  (email not shown publicly)

Journal of phillup (4419)

Tuesday September 28, 2004
06:19 PM

How do you install modules?

[ #21097 ]

I was just reading a post by rafael and it got me thinking about something that I've been wondering about a for a long time.

Mainly, installing Perl modules from a vendor vs. installing via CPAN.

For myself, I usually install almost everything via CPAN... because they don't get updated during normal system updates. That way I've got a chance to run updates on a dev server (and my test scripts) before they make it into production.

In some cases I actually recompile a custom Apache and (mod)Perl specifically so that system updates don't fubar what I've written. (OSX is one such case. The vendor version(s) don't like Mason that well. Panther is better, but I've had problems that were resolved by compiling custom versions.)

Now, one obvious downside is when there might be a serious data damaging (or security) issue... and I haven't kept things up to date.

So... how do others handle module installs? Do you do everything one way... like always use the vendor version unless there isn't one.... a mixture, like installing everthing that requires a compiler using the vendor modules and the rest from CPAN... or is it less "planned" than that?


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 do it like this []. The vendor perl is for vendor-supplied software.

    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • Wow!

      That is a very nice write-up... and, even tho I've installed Perl quite a few times... I definitely picked up a pointer or two.


      The vendor perl is for vendor-supplied software.

      After I got a Mac, with OSX... I started feeling just this way.

      I had not had much problems on my linux boxes, but I've still started doing some of them with custom installs of Apache and Perl (similar to your instructions) just so that I could fiddle more with the OS without having to worry about not being able to get
      • Thank you! Your expression of appreciation made my day!

        I have in the past done custom installs of Perl/Apache for specific applications. For example, when I installed RT a couple of years back, I created an rt user and compiled everything (Perl, MySQL, Apache) as that user, keeping it separate from whatever else was on the system.

        J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
        • Well, RT uses Mason... and, that is what got me started on compiling custom versions.

          I pretty much do Mason stuff all day long. (Writing an application used by a school district.)

          And, there are a suprising number of vendors that ship an Apache/Perl combo that Mason is not totally happy about.
  • Generally I'll install Perl and any updates to it that the vendor releases (in this case, Red Hat) via their up2date/yum package management system. Any additional modules I want installed and/or updated I do via CPAN and track them on a daily basis with a cronjob using my modulereport [] script.

    0 11 * * *  /root/bin/modulereport -rs

    Drops a nice summary of updated/changed modules in my mailbox every morning at 11am (which gives the authors time to get their updates in for the day, and gives me some ti