CVS versus SVN

[n2ize]

Why is it that whenever I get used to using one thing everybody switches over to something else.

I occaisionally need to program stuff and have found a revision control system to be quite handy. The revision control system that I have gotten (finally) used to using is CVS. I setup a CVS server both at home and at work that I can use to manage various projects, including some web related projects.

Now that I have grown reasonably comfortable with CVS it seems everyone is rapidly jumping over to SVN (Subversion).

I understand that there is nothing wrong with sticking to CVS if that is what I am used to and if it works well enough forme.

But,let's say I do decide to switch to SVN.How easy/difficult is the migration process. Is SVN pretty much like CVS and the transition straightforward or, am I going to have to go back to square 1 ,page 1 and restart the mundane task of learning a new revision control system page by page, sentence by sentence ?

Also, how is the installation and configuration process. If I do migrateI'dlike to spend as little time as possible setting up and configuring the whole shebang.

[K7ADB]

I'm in the same boat as you on this one. I've been using CVS for years now and have gotten really used to it. Just as you said though, everyone seems to be switching over to SVN now.

I've asked several friends who have made the switch, what makes SVN better then CVS but so far none have given me a good enough reason to make the switch. You know the saying about "If it aint broke..."

I did find a couple of articles on Google about making the switch. A couple of them are http://w3.pppl.gov/m3d/cvs2svn.html and http://svn.collab.net/repos/svn/trunk/doc/user/cvs-crossover-guide.html There's a lot of CVS-to-SVN crossover guides out there so you might want to check those out too.

[AE6IP]

I've lost count of how many source control systems I'm currently exposed to, but here's my take:

If you're only worried about source control for yourself and what you're using works now, stick with it. If it ain't broke, don't fix it.

If you're contemplating sharing code with others, my condolences, but of the half dozen likely candidates, svn is the one you'll encounter most often.