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.

dbi-proxy is cool 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I gave up asking my sysadmin to install perl modules so I install them myself in a "non-standard" dir and just do a use lib at the beginning of my progs. Not that there is anything wrong with my sysadmin, it's just the whole performance you have to go through to get anything done (i.e create a trouble ticket etc...) is such a pain.

    I like instant gratification :)
    • Yeah, for dev.perl.org [macperl.org] I took to installing all my opwn perl modules for the web services, and access them also via shell services (using PERL5LIB or whatever), and set up CPAN::Config to install things in the right directories, etc. It makes it much easier.
      • We did manage to get a separate, generic user account on most of the machines we needed (in some cases direct login, in some cases sudo).

        Given that, we decided to take it a step further and install our own local version of Perl, not just the modules, on each of the machines. This saved us the hassle of begging for an upgrade if we wanted it, and we don't have to deal with any of the 'use lib' business - it's all under our generic user's home directory.

        It's a little more work on our end to make sure all

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.