Standard practice seems to be to install the modules to a location somewhere in your perl's
@INC and then just let the programs which
use them find them there rather than designating a specific path, either local or centralized. This is, obviously, a variation on "shared".
Regardless of which layout you go with, source control is very highly recommended. svn and cvs are good, reliable solutions for distributed source control, both of which are well-known, widely-used, and can be installed for free on as many machines as needed. If the lack of source control is due to resistance from other developers, you can even install either of them on your local machine to create your own private repository without disturbing anyone else who may think of it as "more trouble than it's worth".
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.