One thing I've found that it is extremely important to be able to recreate exactly the same environment. This is useful for deployment, debugging, etc. We've run into too many problems where we see a problem in production that we can't reproduce in development. That's why want to store perl and the modules in the repo. We also have a global perl install, and it's causing too many problems. For one thing, you can't add/modify a module without potentially disrupting someone else's work, and then keeping dev, test and prod in sync is a pain.

Re: prove... that would be helpful if we had any unit tests. :-)

In reply to Re^2: putting perl and modules in your source code repository by perl5ever
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.