I have been asked to assume maintenance responsibilities for a corporate ActivePerl installation on Win32, and could use some advice.
I know I need to upgrade due to a bug in the currently installed build, but we have already installed a variety of modules that need to stay. I did not perform the original install, and don't know which modules have been added before I took this task. Is searching for the .pm files under the @INC folders really enough? How would you find all the modules an installation of Perl knows about? (For example, we use the Mozilla LDAP SDK, which might be a problem.)
We also have a large body of in-house scripts, which have been placed in a folder under the root Perl folder (called scripts) that are expected to stay there (again, not my call.) So, once I know what modules we need, how can I manage the upgrade and minimize the disruption to the users?
Useful tips on maintaining a Perl installtion (or links that provide said info. are certainly welcome.)
Thanks!
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.