I'm working on a large perl application that's been around for a while, and one thing we've discovered is that we need to put the source for perl itself and the CPAN modules we are using in our source code repository with our app.

I was wondering if any had any experience or ideas of how to do this so we don't have to rebuild perl and the modules all the time. The set of modules doesn't change very often, but at runtime we want to be as sure as we can that the module tree we are using is as specified in the repository.

Does anyone have any experience with this? Do we commit the module packages (.tar.gz files) into the repo, or do we commit the files from the installed module tree? 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? Thanks!

In reply to 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.