Since you've already got lots of great answers on the directory structure side of things, I thought I'd offer my opinions on the issue of CVS. As to (CVS) modules, what we use here is one (CVS) module per project, plus one (CVS) module for the common (Perl) modules.
Personally, I think using MakeMaker for this type of thing is overkill. You don't have to worry about possible installation of your modules on hundreds of obscure flavors of Unix-oid OSes ... just on one machine, and you know that one pretty well. I would go with mandog's suggestion of each project having its own install script. The way we do it here at my company is to have a single script called "rel" to release things, but of course it has to have a buttload of configuration files to tell it where things go and whatnot. Personally, I'm starting to think we should have done it the way mandog suggests too.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||