I don't know that there is a 'right' answer to your question/s, but I do know what I would do if I were in your shoes. Seems to me that you have two problems, one is replicating a working solution and the other is updating 'parts' as they change. To handle the first I would go ahead with your list of '.gz' files, except I would use it to power a perl script to automate the install procedure. It would do for each .gz the usual make this that and the other thing---all in the correct location probably from a tempory directory, then cleaning up afterwards. There may be some 'hand' work left afterwards, but if it is invariant, then script it back into your build process. Generalize this so that you can point at whatever box you need to and you should have a leg up on the first problem. The second would require monitoring the CPAN published list looking for hits---from which you could do the appropiate thing, dl, etc. I'd also do all of this with an eye towards doing as little as possible in order to get the job done, as it seems to me that in your case, 'least change' is probably 'best change'...

--hsm

"Never try to teach a pig to sing...it wastes your time and it annoys the pig."

In reply to Re: Maintaining CPAN sources for later installation across multiple servers by hsmyers
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.