Personally, I'd prefer to let CPAN do the source-control on those modules and install the specific version of a given module in each place. For example, you could either d/l the correct .tar.gz or do "install XXX 1.234" within the CPAN module.

The problem with this approach is that you cannot trust CPAN to have that version available. Old modules are deleted on a regular basis by their authors (I certainly do). I have a vague memory of this being a "best practice" documented somewhere, but I can't locate it after five minutes googling so I may be mis-remembering.

Yes, there are things like backpan, but now you have to deal with CPAN, backpan + your own modules. I'm in complete agreement with chromatic, keeping everything in source control makes development much easier IMHO.

My /vendor directory of my current project includes all third party modules, plus perl, apache, mod_perl, openssl, and all other third party code. I want everything that I need to build my project available locally and under source control so that I can access it easily at any point in the future.

In reply to Re^5: Moving Perl from test to Dev by adrianh
in thread Moving Perl from test to Dev by Anonymous Monk

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.