Productive Linux


 Subscribe via Feedburner in a reader

Enter your email address:

Delivered by FeedBurner


Don't have an account?
Sign up to
Forgot your password?

Moving from svn to svk
4 December 2006 @ 15:25 GMT
by Paul

Subversion is the tool of choice for version control systems. On the client side, I've heard loads of people saying that I should move to svk from svn. I groaned. I hate learning new tools. The ones I'm using are good enough, thank you very mucn.

But then something silly happened. One of the scripts (not one that I wrote, I'd hasten to add) in a project I'm working on ran amok and deleted part of the local repository including those essential .svn files that keep vital information.

That was when it was time to checkout (no pun intended) svk. The problem is, as I feared, svk is quite different. There's something called 'depot paths'. There's a 'depotmap'. But what really struck me was how the 'checkout' commands are totally different. With svn you do:

svn co svn://path/to/depository directoryname

With svk it's something like:

svk mirror svn://dep.osi.tory/address //depot/path
svk sync //depot/path
svk checkout //depot/path/trunk

Read why here. Of course, svk does allow you to do it the old-fashioned svn, or indeed cvs, way as well. But I have been using which kept crashing. It is during these crashes that the checkout process can go awry. So, I had to learn how to do it the svk way, so that I could retrace the steps and make it work better. Despite being a bit harder to use, it is clear to me that svk is the better tool.

Comments disabled