comment on

svk looks promising, but personally, I don't think the documentation is there, yet. Whereas with subversion, there's the fantastic Subversion Book. Download, print, read and go. Perhaps somewhere down the line I'll feel that svk is worth a second look. The OP was looking for guidelines on future projects -- from a fresh start, I'd second taking a good hard look at subversion.

Regarding the migration challenge, the Subversion book includes an appendix on Subversion for CVS Users, which also discusses the latest tools for migrating a CVS directory to subversion.

-xdg

Code posted by xdg on PerlMonks is public domain. It has no warranties, express or implied. Posted code may not have been tested. Use at your own risk.

In reply to Re^3: Tips for managing Perl projects? by xdg
in thread Tips for managing Perl projects? by radiantmatrix

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.


Do you know where your variables are?
	PerlMonks