...
A nice online manual of SVN usage and theory is located here.
SVN Command Primer
SVN
...
An SVN Repository has been created at /afs/slac.stanford.edu/g/scs/net/netmon/repo/svn. The command to create this was:
| Code Block |
|---|
$ svnadmin create /afs/slac.stanford.edu/g/scs/net/netmon/repo/svn --fs-type fsfs
|
Note that we are using fs-type fsfs due to the fact that we are housing the repo on an AFS share.
SVN Project Creation
New projects can be created by IEPM members (with sufficient AFS permissions). Given an existing project with files to be imported, one would run the command:
| Code Block |
|---|
$ cd <project-path>
$ svn import . file:///afs/slac.stanford.edu/g/scs/net/netmon/repo/svn/<project-name>/trunk
|
This will recusively add all files within <project-path> into the SVN repositry; whereby it will be located at <project-name>.
The use of /trunk at the end of the path is arbitary; however, it is recommended good practise to facilitate the branching of projects.
Once a project has been initially imported into the SVN database, it is necessary to start working on a 'fresh' version (as the files in the initial import do not 'know' about the SVN). This is achieved with a SVN checkout.
SVN Checkout
In order to work on SVN projects, it is necessary to 'checkout' the project files. Given a project, you are expected to work on edits on a local copy from which editing and testing is to occur before the changes are 'checked in' back into the SVN repository.
...