Releases

Current version
Git/Latestdiff: 1.5.6

Latest Snapshots
Produced after each commit or rebase to new upstream version

GIT
RSBAC source code, can be unstable sometimes

Events

No events planned

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

--- documentation:svk [2005/09/20 07:50] – (old revision restored) 127.0.0.1
+++ documentation:svk [2006/06/02 11:02] (current) – removed kang
@@ Line 1: / Line 1: @@
-===== What is SVK =====
-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 locally, then submit to the repository when you are done. So, it allows to work offline.
-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.
-===== Getting started, mirroring a repository =====
-So let's initialise where to keep the local repository (the depot):
-<code>
-# svk depotmap --init
-</code>
-You can choose where to put or change the location of this depot with the relocate command:
-<code>
-# svk depotmap --relocate /path/to/somewhere
-</code>
-We will now mirror an existing SVN repository, RSBAC's for instance:
-Let's create a path just for mirrors. Put whatever you feel like as commit message when asked.
-<code>
-# svk mkdir //mirrors
-</code>
-Now create the mirrored path:
-//For anonymous mirroring//
-<code>
-# svk mirror svn://svn.rsbac.mprivacy-update.de/rsbac1 //mirrors/rsbac1
-</code>
-//For developers with write access//
-<code>
-# svn+ssh://subversion@mprivacy-update.de/daten/subversion/rsbac1 //mirrors/rsbac1
-</code>
-And synchronise it:
-<code>
-# svk sync //mirrors/rsbac1
-</code>
-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.
-===== Making a local branch, working offline =====
-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 :-))
-So, create a directory for the local branches, and create one for rsbac1:
-<code>
-# svk mkdir //local
-# svk cp //mirrors/rsbac1 //local/rsbac1"
-</code>
-You can now checkout "//local/rsbac1" or any part of it (like "//local/rsbac1/linux-kernel/2.6/branches/linux-rsbac"), modify, commit (using "svk commit", 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)
-<code>
-# svk push //local/rsbac1
-</code>
-You can also get the changes from the mirror to update your local branch:
-<code>
-# svk pull //local/rsbac1
-</code>
-===== Signing =====
-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, or push command.
-<code>
-# svk push -S //local/rsbac1
-</code>
-You can verify thoses signatures with the verify command
-<code>
-# svk verify -r revision
-</code>

//