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.
HTH.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
