SVK is available from http://svk.elixus.org/ It is a “distributed” Version Control tool. It uses FSFS from SVN as it's sublayer. From a 10,000 feet view, SVK allows to checkout any SVN/CVS/Perforce/Git repository to your local machine and commit/checkout remotely and locally, then submit the changes when you are done. So, it allows to work offline. And it allows to work on your very own branches, for testing.

From a more technical point of view, SVK is like a repository on your local machine where you have two kinds of sub-repositories: Mirrors of SVN/CVS/… or local branches.

Here's a diagram showing how this little world works: SVK overview diagram.

So let's initialise where to keep the local repository (the depot):

# svk depotmap --init

You can choose where to put or change the location of this depot with the relocate command:

# svk depotmap --relocate /path/to/somewhere

You will probably want to make a depot dedicated to RSBAC, so that you can mess with it without destroying other depots.

# svk depotmap rsbac /home/youruser/.svk/rsbac
(or anywhere else)

We will now mirrors the RSBAC SVN repositories:

For anonymous mirroring

# svk mirror svn://rsbac.org/rsbac-2.6 /rsbac/rsbac-2.6
# svk mirror svn://rsbac.org/rsbac-admin /rsbac/rsbac-admin

For developers with write access

# svn+ssh://<you@>rsbac.org/daten/subversion/rsbac-2.6 /rsbac/rsbac-2.6
# svn+ssh://<you@>rsbac.org/daten/subversion/rsbac-2.4 /rsbac/rsbac-2.4
# svn+ssh://<you@>rsbac.org/daten/subversion/rsbac-admin /rsbac/rsbac-admin

And synchronise it:

# svk sync -a

When committing or using this path directly, changes will affect the real SVN repository directly, much like using SVN would do.

Whenever you want to checkout this path, just do it. You can delete the files afterwards and check them out again, or you can simply update then. There will be no “.svn” directories or the like. SVK is just flexible.

To work offline or just do your stuff without affecting the repository directly, you've to create a local branch. Once you are done with your work you can commit it to the mirrored path, or create a patch if you have no write access (and send it to us ) Basically the repository already lives on your harddrive so just make this branch whenever you are really offline, or have no write access.

So, create a directory for the local branches, and create your branch (example for the 2.6 RSBAC kernel):

# svk mkdir //local
# svk cp //mirrors/rsbac1/linux-kernel/2.6/branches/linux-rsbac //local/26/linux-rsbac"

You can now checkout “//local/26/linux-rsbac”, modify, commit (using “svk commit -S”, please never ever use svn on svk local repository, it would corrupt it.)

Once done, you have to merge back your local branch to the mirrored path (this will commit your changes to the real SVN repository)

# svk smerge //local/26/linux-rsbac //mirrors/rsbac1/linux-kernel/2.6/branches/linux-rsbac

note: ONLY USE push IF YOU KNOW WHAT YOU ARE DOING.

You can also get the changes from the mirror to update your local branch with upstream:

Specify the path even if its optional or I will kill you personally. I'm not kidding.

# svk pull //local/26/linux-rsbac

If you are a RSBAC developper, please do not forget to sign every commit made to the mirrored path!

Simply add “-S” to every commit, smerge, merge, or other commit-like command.

# svk commit -S myfile.c

You can verify those signatures with the verify command

# svk verify -r REVISION

There are several ways to specify an SVK version. Let's take a look at the log:

# svk log -r HEAD //rsbac1
----------------------------------------------------------------------
r220 (orig r208):  subversion | 2005-09-22 11:08:08 +0200

kang: added possibility to change the default branch (SVKDEFBRANCH=linux-rsbac-1
.2|linux-rsbac)
----------------------------------------------------------------------

r220 is your local SVK revision number. you can use it anytime, but its only yours. r208 is SVN's revision number. If you want to talk about this very change to someone, PLEASE give this revision number.

In short, to see a diff from this change on your system:

# svk diff -r220:219

To see a diff on this change, for anyone, including you:

# svk diff -r208@:207@

See the “@” at the end ? that does the trick.

When diffing a file on your filesystem against the mirrored repository latest's version, you can simply do:

# svk diff -rBASE:HEAD myfile

It will return the changes in the mirrored repository, not yet in your local file.

The reverse, to see what's in your file and not in the repository, is quite easy:

# svk diff myfile

You can also specify revision per date:

# svk log -r {2005-09-22}

For more information, see the SVK website, or the very good SVK book.