A Quick SVN Reference:

SVN Home: http://subversion.tigris.org/
SVN Book: http://svnbook.red-bean.com/
CVS2SVN : http://cvs2svn.tigris.org/


NOTE: cvs2svn is no longer a part of the SVN codebase!!!


Converting CVS to SVN:

1) Check out and install SVN.
2) Check out the cvs2svn source:
 # svn co http://svn.collab.net/repos/cvs2svn/trunk/
3) Run the conversion like this:
 # ./cvs2svn.py --trunk-only --create -s  /opt/cuddlesvn /opt/cvsroot
	Where /opt/cuddlesvn is there you want your SVN repos based
	and /opt/cvsroot is your current CVSROOT
4) Done!


Creating an Empty SVN Repo:

1) ...

Configuring SVN:
1) In $(SVNROOT)/conf create 2 files...
2) Create the file svnserve.conf

root@nexus6 conf$ cat svnserve.conf 
### Cuddletech Internal SVN Server Configuration [4/22/04]

[general]
### These options control access to the repository for unauthenticated
### and authenticated users.  Valid values are "write", "read",
### and "none".  The sample settings below are the defaults.
anon-access = read
auth-access = write

password-db = passwd.svn
realm = Cuddletech SVN

3) Create the file passwd.svn (or whatever you named it above):
root@nexus6 conf$ cat passwd.svn 
## Cuddletech SVN Passwd File

[users]
benr = passwd

4) No you can start a stand alone SVN server: /usr/local/bin/svnserve -d

NOTE: For other methods of creating an SVN server, see the documentation.





---------------------------------------------
USING SVN
---------------------------------------------

--> Normal duty cyle:

[benr@nexus tekref]$ vi svn.ref.txt
[benr@nexus tekref]$ svn status
?      svn.ref.txt
M      iSCSI/iscsiref.xml
[benr@nexus tekref]$ svn add svn.ref.txt 
A         svn.ref.txt
[benr@nexus tekref]$ svn update
At revision 422.
[benr@nexus tekref]$ export SVN_EDITOR="vi"
[benr@nexus tekref]$ svn commit
Authentication realm: <svn://host:3690> Cuddletech SVN
Password for 'benr': 
Sending        iSCSI/iscsiref.xml
Adding         svn.ref.txt
Transmitting file data ..
Committed revision 423.

NOTES:
	As a CVS user you want to use the update command all the time.
	Do not.  It's not needed in SVN.  Use Status to see whats
	changed, and commit to send it.

	------

--> Creating Patches from the working directory:

[benr@nexus tekref]$ svn diff >patch
[benr@nexus tekref]$ head patch 
Index: svn.ref.txt
===================================================================
--- svn.ref.txt (revision 423)
+++ svn.ref.txt (working copy)
@@ -57,9 +57,29 @@
 
 
 ---------------------------------------------
+USING SVN
+---------------------------------------------
[benr@nexus tekref]$ 


--> Calculating the diff between version versions
[benr@nexus tekref]$ svn log nis.linux.ref 
------------------------------------------------------------------------
r91 | benr | 2001-12-09 02:36:09 -0800 (Sun, 09 Dec 2001) | 2 lines

updates........

------------------------------------------------------------------------
r90 | benr | 2001-12-06 21:48:44 -0800 (Thu, 06 Dec 2001) | 2 lines

More shit.

------------------------------------------------------------------------
r89 | benr | 2001-12-06 19:57:27 -0800 (Thu, 06 Dec 2001) | 2 lines

Niss teckref

------------------------------------------------------------------------
[benr@nexus tekref]$ svn di -r 90:91 nis.linux.ref 
Index: nis.linux.ref
===================================================================
--- nis.linux.ref       (revision 90)
+++ nis.linux.ref       (revision 91)
@@ -210,3 +210,14 @@
 
 -----------------------------------------------------------------------------
 
+How to Update your maps
+-----------------------
+
+Updating maps is a very simple proccess.  Simply modify the /etc/ file
+you want to change on the master server, and then run "make" in the /var/yp
+directory.  This will update the maps that changed and transfer the map 
+to the slave servers listed in /var/yp/ypservers.
+
+
+-----------------------------------------------------------------------------
+