ACPI administration advocacy advocacy advocacy opinion alsa amarok apache apple apt aptitude archive audio audo authentication automount avi awk backup bash BIOS boot browser business bzip cache calendar calibre cdr cdrecord censorship commandline computerscience console convert cron cut database date debian degree design desktop development disk dpkg dvd economics education emacs email europe exim faad ffmpeg file files firefox firewall flash foss freedom ftp fun fuse git gnumeric graphics grep growisofs grub gtkpod gzip hardware hardware html icedove idiocy image imagemagick images installation ip iphone ipod iptables iso itunes ivman kde kernel keyboard knoppix lame laptop latex libreoffice linux locale lockin locking longlines lsof m4a microsoft mimetypes minitab mogrify mount mp3 mp4 mplayer multimedia music mysql network nfs nfs4 nmap openbox openfiles openoffice opinion opinion orgmode partition pdf pdftk perl php podcast politics pomodoro ports postgresql print printing privacy process programming rant remote rhythmbox rss rsync rxvt scp screengrab screenshot script scripting scsi security sed server services shell siteadmin sitenews sitesoftware skype skype slackware sound sox spam spreadsheet ssh statistics subversion sudo svk swap t23 t43 tar terminal tex text thinkpad thunderbird time timer timezone ubuntu udev upgrade usb usbmount users uuid versioncontrol vfat video vnc windows wine wordpress wordprocessing X40 xwindows xwindows youtube
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 Sourceforge.net 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.