I'm not sure that this approach would work as you anticipate: installation of modules might require advanced privileges. It also seems clumsy to me to try to do this in this way. Instead, I am reminded of the simple
REQUIREMENTS.TXT strategy that is used with Python. Perhaps you could write a script that scans your Perl source-code looking for
use statements and extracting the module names. Then, manually sort and de-dupe the list and winnow out the builtins. Now, another simple script could read that file and attempt to install all of the modules therein listed. This is done one time at installation time ... by hand. The essential idea is very simple and it works quite well.
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.