We standardize on a perl verison/build and build CPAN modules against it. We will test it on our boxes first and make patches if needed. When it works we will save off the blib directory from the built module, copy it into our custom module, and store it in our repo (remember to turn off keyword expansion or any other file changing operations in your repo). Then we use a special Makefile.pl that only installs the contents the blib directory. The only conflicts we see is the .exists files.

If you want to keep the original source around you can stuff the tar.gz files into the repo. We don't do that and will go back out to CPAN for the versions we need. Few times we couldn't find a older one, but found out that the new version was better for us anyways.

And what would be a good way to determine if a previous build of perl and modules is compatible with the needs of the current app source code?"

Testing. However, unless there is some major changes to the module, then you won't find too many issues.

In reply to Re: putting perl and modules in your source code repository by admiral_grinder
in thread putting perl and modules in your source code repository by perl5ever

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.