in reply to Re: Learning How to Use CVS for Personal Perl Coding Practices
in thread Learning How to Use CVS for Personal Perl Coding Practices
I think the biggest selling point of any SCCS is what you might do with it in the future. Considering I have an account on SourceForge, and that they use CVS, using CVS for my personal perl projects makes sense as I'll be able to leverage all my experience using cvs with SourceForge with what I'm doing outside of SourceForge; I'll be able to create a project on SourceForge and move my repository over; and if/when I do so, I won't need to change anything that I'm doing in order to use it.
I know there are a number of open-source SCCS repositories found on the 'net now. But I would suggest that using what they use (whichever one of "they" that you choose) will make life easier should you ever want to put your project up there to collaborate with others.
Update: This isn't an argument against Subversion. Just a warning to educate yourself on what you may want to do in the future before committing to something now ;-) (It isn't even meant to be an advertisement for sourceforge ;-})
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Learning How to Use CVS for Personal Perl Coding Practices
by tirwhan (Abbot) on Nov 03, 2005 at 16:55 UTC | |
|
Re^3: Learning How to Use CVS for Personal Perl Coding Practices
by tphyahoo (Vicar) on Nov 03, 2005 at 17:12 UTC |