1) I would identify through testing the absolute earliest version your code can tolerate. But then I would investigate (by testing against even earlier versions) what the impact would be of modifying code to push that limit backwards to allow as many sites as possible to be able to use the suite in question and make a feasibility decision as to what the earliest version should be.

2) A 'require ' + version (e.g. require 5.004;) prevents a script running in an environment earlier than the earliest version your policy then supports.

3) Module FindBin::libs offers automated ways to load lib directories into @INC/%INC without any minimised (hard-) coding (you have to tell it where to start recursively searching for modules).

-M

Free your mind

In reply to Re: Deployment Qs by Moron
in thread Deployment Qs by ph713

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!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            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.