An alternative is the
Aegis
change management system.
Aegis uses a very different model than CVS,
although it can be configured
to use RCS
as its underlying source code control system,
in much the same way that CVS wraps the RCS functionality.
Aegis manages and enforces testing conventions in very much
the way you describe--that is, it can run tests with references to
copies of things already checked in to the repository.
It does more for you, although you have to buy into its
model of the development cycle.
If you do, though, it's very powerful.
Setting up Aegis for Perl module development is a little
tricky, but a solved problem.
(Recently, Michael G. Schwern has started using it
for module development.)
I'd be happy to assist anyone who wants to give it a try.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.