I guess you might be worried about custom modules... Just back up all directories in you @INC path (that the one that gets printed out when perl can't find a module). Then upgrade.
Depending on how zealous your package manager is about cleaning up, the modules may or may not be there after the upgrade.
There is no reason to keep old modules if they are still available on CPAN. Backing them up in case somebody made a booboo with the new version of the module may be a good idea, though.
If it were me, I'd just do the upgrade, then deal with the 'missing module' errors as they come. Since perl is very clear about which modules it needs, it should be an easy task to reinstall them. I never knew there was a log of installed modules, but that would be a good way to do it.
____________________
Jeremy
I didn't believe in evil until I dated it.
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.