My preference is to install a separate perl for these reasons.
- The system is never broken by an upgrade to a module. Most Linux distributions come with Perl scripts for system tasks, you don't want to maintain those.
- You can upgrade the version of Perl without breaking the system, you don't have to track down all the modules used by the distribution scripts
- You can install multiple versions in parallel.
- The Perl build can be customized for your usage. Don't use threads? Don't build it.
Whatever you choose to do, you need a process to track what CPAN modules are deployed so that you can reproduce your environment whenever you upgrade Perl or deploy to a new machine.
You also need a process for deployment into test and production. You can't deploy an upgraded module or version of Perl whilst it is being used by the system. Personally I prefer that the sysadmins be responsible for deployment to production as we have those procedures (They involve outage windows at god awful times;)
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.