You have nothing to gain by making separate installations unless you intend to use these modules in separate places.
Hmm. I sometimes develop in this way. You do get some useful things from this model:
-
You can easily separate the test scripts that apply to this particular module from those that apply to another. This allows you to easily run only the relevant tests when testing a module. This can save time and make TDD considerably more pleasant.
-
People can work on modules independently from each other.
- It can give you a nice clear separation of unit tests (distributed with module directory) and acceptance tests (distributed with application as a whole).
- Allows you to easily release module updates rather than application updates as appropriate.
There are certainly other ways of getting these benefits, but the CPAN-ish structure gets you a lot without any effort.
-
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.
|
