Remove anoncvs instructions and replace them with svnanon instructions.

(This used to be commit 0fe4774a4ffa0ddccb68b2e28a834d00dcbe3c84)

1 files changed, 33 insertions, 58 deletions

diff --git a/docs/howto/Compiling.xml b/docs/howto/Compiling.xml
index a74d2ebcd2..9ffd3dfb6a 100644
--- a/docs/howto/Compiling.xml
+++ b/docs/howto/Compiling.xml
@@ -13,48 +13,48 @@
 <para>
 You can obtain the Samba source from the
 <ulink url="http://samba.org/">Samba Website.</ulink> To obtain a development version, 
-you can download Samba from CVS or using <command>rsync</command>.
+you can download Samba from Subversion or using <command>rsync</command>.
 </para>
 
 <sect1>
-<title>Access Samba Source Code via CVS</title>
+<title>Access Samba Source Code via Subversion</title>
 
 
 <sect2>
 <title>Introduction</title>
 
 <para>
-<indexterm><primary>CVS</primary></indexterm>
-Samba is developed in an open environment. Developers use
-Concurrent Versioning System (CVS) to <quote>checkin</quote> (also known as 
-<quote>commit</quote>) new source code. Samba's various CVS branches can
-be accessed via anonymous CVS using the instructions
+<indexterm><primary>Subversion</primary></indexterm>
+Samba is developed in an open environment. Developers use a
+Subversion to <quote>checkin</quote> (also known as 
+<quote>commit</quote>) new source code. Samba's various Subversion branches can
+be accessed via anonymous Subversion using the instructions
 detailed in this chapter.
 </para>
 
 <para>
 This chapter is a modified version of the instructions found at the
-<ulink noescape="1" url="http://samba.org/samba/cvs.html">Samba</ulink> web site.
+<ulink noescape="1" url="http://samba.org/samba/subversion.html">Samba</ulink> web site.
 </para>
 
 </sect2>
 
 <sect2>
-<title>CVS Access to samba.org</title>
+<title>Subversion Access to samba.org</title>
 
 <para>
-The machine samba.org runs a publicly accessible CVS 
+The machine samba.org runs a publicly accessible Subversion
 repository for access to the source code of several packages, 
 including Samba, rsync, distcc, ccache, and jitterbug. There are two main ways
-of accessing the CVS server on this host:
+of accessing the Subversion server on this host:
 </para>
 
 <sect3>
-<title>Access via CVSweb</title>
+<title>Access via SVNweb</title>
 
 
 <para>
-<indexterm><primary>CVS</primary><secondary>web</secondary></indexterm>
+<indexterm><primary>SVN</primary><secondary>web</secondary></indexterm>
 You can access the source code via your favorite WWW browser. This allows you to access
 the contents of individual files in the repository and also to look at the revision 
 history and commit logs of individual files. You can also ask for a diff 
@@ -63,63 +63,38 @@ listing between any two versions on the repository.
 
 <para>
 Use the URL:
-<ulink noescape="1" url="http://samba.org/cgi-bin/CVSweb">http://samba.org/cgi-bin/CVSweb</ulink>
+<ulink noescape="1" url="http://svnweb.samba.org/">http://svnweb.samba.org/</ulink>
 </para>
 </sect3>
 
 <sect3>
-<title>Access via CVS</title>
+<title>Access via Subversion</title>
 
 <para>
 You can also access the source code via a 
-normal CVS client. This gives you much more control over what you can 
+normal Subversion client. This gives you much more control over what you can 
 do with the repository and allows you to checkout whole source trees 
-and keep them up-to-date via normal CVS commands. This is the 
+and keep them up-to-date via normal Subversion commands. This is the 
 preferred method of access if you are a developer and not
 just a casual browser.
 </para>
 
-<para>
-To download the latest CVS source code, point your
-browser at the URL :
-<ulink noescape="1" url="http://www.cyclic.com/">http://www.cyclic.com/</ulink>.
-and click on the <quote>How to get CVS</quote> link. CVS is free software under 
-the GNU GPL (as is Samba). Note that there are several graphical CVS clients
-that provide a graphical interface to the sometimes mundane CVS commands.
-Links to theses clients are also available from the Cyclic Web site.
+<para>In order to be able to download the Samba sources off Subversion, you need 
+a Subversion client. Your distribution might include one, or you can download the 
+sources from <ulink noescape="1" url="http://subversion.tigris.org/">http://subversion.tigris.org/</ulink>.
 </para>
 
 <para>
-To gain access via anonymous CVS, use the following steps. 
-For this example it is assumed that you want a copy of the 
-Samba source code. For the other source code repositories 
-on this system just substitute the correct package name.
+To gain access via anonymous Subversion, use the following steps. 
 </para>
 
 <procedure>
-	<title>Retrieving Samba using CVS</title>
-
-	<step>
-	<para>
-	Install a recent copy of CVS. All you really need is a 
-	copy of the CVS client binary. 
-	</para>
-	</step>
+	<title>Retrieving Samba using Subversion</title>
 
 	<step>
 	<para>
-	Run the command:
-	</para>
-
-	<para>
-	<userinput>cvs -d :pserver:cvs@samba.org:/cvsroot login</userinput>
-	</para>
-	</step>
-
-	<step>
-	
-	<para>
-	When it asks you for a password, type <userinput>cvs</userinput>.
+	Install a recent copy of Subversion. All you really need is a 
+	copy of the Subversion client binary. 
 	</para>
 	</step>
 
@@ -129,25 +104,25 @@ on this system just substitute the correct package name.
 	</para>
 	
 	<para>
-	<userinput>cvs -d :pserver:CVS@samba.org:/cvsroot co samba</userinput>.
+	<userinput>svn co svn://svnanon.samba.org/samba/trunk samba</userinput>.
 	</para>
 	
 	<para>
 	This will create a directory called <filename>samba</filename> containing the 
-	latest Samba source code (i.e., the HEAD tagged CVS branch). This 
-	currently corresponds to the 3.0 development tree. 
+	latest Samba source code (usually the branch that is going to be the next major release). This 
+	currently corresponds to the 3.1 development tree. 
 	</para>
 	
 	<para>
-	CVS branches other then HEAD can be obtained by using the
-	<option>-r</option> and defining a tag name. A list of branch tag names 
+		Subversion branches other then trunk can be obtained by adding branches/BRANCH_NAME
+	to the URL you check out. A list of branch names 
 	can be found on the <quote>Development</quote> page of the Samba Web site. A common
 	request is to obtain the latest 3.0 release code. This could be done by 
 	using the following command:
 	</para>
 	
 	<para>
-	<userinput>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_3_0 samba</userinput>.
+		<userinput>svn co svn://svnanon.samba.org/samba/branches/SAMBA_3_0 samba_3</userinput>.
 	</para>
 	</step>
 
@@ -158,7 +133,7 @@ on this system just substitute the correct package name.
 	</para>
 	
 	<para>
-	<userinput>cvs update -d -P</userinput>
+	<userinput>svn update</userinput>
 	</para>
 	</step>
 </procedure>
@@ -175,7 +150,7 @@ on this system just substitute the correct package name.
 	<para>
 	<indexterm><primary>rsync</primary></indexterm>
 	<indexterm><primary>ftp</primary></indexterm>
-	<parameter>pserver.samba.org</parameter> also exports unpacked copies of most parts of the CVS
+	<parameter>pserver.samba.org</parameter> also exports unpacked copies of most parts of the Subversion 
 	tree at the Samba <ulink noescape="1" url="ftp://pserver.samba.org/pub/unpacked">pserver</ulink> 
 	location and also via anonymous rsync at the Samba
 	<ulink noescape="1" url="rsync://pserver.samba.org/ftp/unpacked/">rsync</ulink> server location. 
@@ -185,7 +160,7 @@ on this system just substitute the correct package name.
 
 	<para>
 	The disadvantage of the unpacked trees is that they do not support automatic
-	merging of local changes like CVS does. <command>rsync</command> access is most convenient 
+	merging of local changes like Subversion does. <command>rsync</command> access is most convenient 
 	for an initial install.                      
 	</para>
 </sect1>