But currently the instance scripts, templates, and modules are all version controlled as individual files, with nothing linking them as one "application".
One thing that has helped me do this is to treat everything as a CPAN distribution. I use Module::Build which is pureperl (unlike ExtUtils::MakeMaker which builds Makefiles). It's also completely extensible, though the documentation could use a little work. So, if each of your items is their own distro, you can have the actual app's Build.PL indicate that it depends on Foo, Bar, and Baz, each having a minimum version. It also allows you to verify all your CPAN installs, the Perl version, and anything else you might need. Then, you put the Build.PL into SVN and you're good to go.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
-
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.
|
