Well, a week is not a lot of time to debug possible breakage of multiple scripts over hundreds of installed modules. I hope you have a good test suite :)
CPAN does store old versions of modules (many, not all) so if you have a record of versions, you may be able to recover the original software. Also, packages are stored in the authors directory of the cpan working directory -- if you do not clean that out often, then you may find copies there.
Probably the easiest approach is to hand build on one machine, checking for errors (you need to do this, because while the modules are unchamged, the compiler, glibc, etc. may be) and then rsync to the other machines.
Note that many of the modules you find may already be installed as part of the core libraries of perl. It would be easier if you surveyed the scripts to see exactly which modules are use'd or require'd. It may be fewer than you think.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.