Perhaps you have too many modules for this to be efficient, but source code control can be used to deal with this problem. During the development phase you keep everything new or added under source control, and later for install all you do is run the standard perl install (for me this means installing a given version of AS perl) and then a "get latest version" into the approprate location and presto your done. Source control also gives you the easy ability to look for unauthorized changes, snap shots, etc. For instance config files and the like can be kept under source control to make tracking errors and changes easier.


---
demerphq


In reply to Re: Maintaining CPAN sources for later installation across multiple servers by demerphq
in thread Maintaining CPAN sources for later installation across multiple servers by mp

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.