Usually there is some very-important production system that is absolutely dependent, source-code wise, on some early version of Perl.   What I suggest that people should do in that case is to define an environment-variable in the production context, named, say, $PERL_CMD.   This variable is hard-coded to the Perl interpreter needed by this program, which, in turn, has been hard configured to refer to an isolated set of CPAN libraries which it, itself, has built ... i.e. without resorting to PERL5LIB, which of course also is given a known value.   Every script invokes Perl by reference to $PERL_CMD.   What you achieve by doing this is to isolate the Perl that this system relies-on from the system at large.   You include all of the scripts, and all of the documentation, in the source-code control system tree for that app.

This, if done correctly, relieves you from the obligation to keep “the system at large” at an older level, and it also circumvents any interdependency between two similar apps that might both need to run on the same boxes.   The only “cost,” which becomes inconsequential through the use of SANs and so-forth, is disk space.

It does get a little bit more interesting when the distro-maintenance software for a Linux system also runs in Perl, as many do.   To handle this case, newer versions of Perl can be set up in /usr/local/whatever.   It does, alas, get a little bit messy at times.


In reply to Re: Roll Call - How new is your Perl? by sundialsvc4
in thread Roll Call - How new is your Perl? by Tommy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.