Either you have
1. One project with several modules/files.
Use Git or Subversion. If one programmer broke the code, you will be able to revert this change.
If you are not sure if programmer break code or no - use unit/integration tests.
2. One project with several files, but you wish to distribute different files/modules independently. Different computers/module users will have different versions of modules installed.
Then you need put version for each module, and think about compatibility between version. This is about release management, and much more complicated that (1). Example is CPAN
Try use (1).
Also if your files/modules contain perl 'packages' use 'use', not require, unless you have good reason (for example, you decide runtime which module to load)
And always use version control systems (like Subversion/Git/Mercurial etc) unless you're writing something very very small to be deployed on one computer and you are alone.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||