replaced CVS instructions with Subversion

livesupport/doc/gettingStarted.html

@@ -89,15 +89,15 @@ XMLv2 module for PHP<br>
   </li>
   <li><a href="http://www.postgresql.org/">PostgreSQL</a> support in PHP</li>
   <li><a href="http://pear.php.net/">PEAR</a> </li>
-<!--  <li><a href="http:///"></a></li>-->
 </ul>
+
 <h2>Check out the sources</h2>
-The LiveSupport development directory tree can be accessed via
-anonymous <a href="https://www.cvshome.org/">CVS</a>, using the
-CVSROOT <code>:pserver:anonymous@netfinity-5.mdlf.org:/home/cvs</code>.
-The repository is called livesupport, thus the following CVS command
-would check out the development tree:<br>
-<pre><code><br>cvs -z3 -d </code><code>:pserver:anonymous@netfinity-5.mdlf.org:/home/cvs checkout livesupport<br><br></code></pre>
+The LiveSupport development directory tree can be accessed anonymously via
+<a href="http://subversion.tigris.org/">Subversion</a>, at
+<code>svn+ssh://code.campware.org/home/svn/repo/livesupport/trunk/livesupport</code>.
+The following Subversion command
+would check out the development tree:<br><br>
+<pre><code>svn checkout svn+ssh://code.campware.org/home/svn/repo/livesupport/trunk/livesupport</code></pre><br>
 This will check out and create the LiveSupport development <a
  href="developmentEnvironment/directoryStructure.html">directory
 structure</a>.<br>
@@ -120,6 +120,7 @@ development. In the former case, only one database instance, scheduler
 daemon and apache (XML-RPC and HTTP/HTML) entry point is needed. In the
 latter case, each user will have their own database instance, scheduler
 daemon and apache entry points.<br>
+
 <h3>Only one developer doing development on the system<br>
 </h3>
 If only one developer is doing development on the system, there is no
@@ -139,26 +140,27 @@ regularly create and destroy database tables.<br>
 <br>
 The scheduler daemon will use the port 3344.<br>
 <br>
-Please, check settings in <code>var/conf.php</code> files in both
-storageServer and archiveServer modules and create two
-symlinks with name corresponding to 'URL configuration' part of
-<code>var/conf.php</code> files - example for default values:
+Please check settings in <code>var/conf.php</code> files in both
+the storageServer and archiveServer modules and create two
+symlinks with name corresponding to the 'URL configuration' part of
+<code>var/conf.php</code> files.  Here is an example for default values:
 <ul>
   <li> <code>http://localhost:80/livesupportStorageServer/</code>
-should point to the <code>&lt;livesupport-cvs&gt;/modules/storageServer/var</code>
+should point to the <code>&lt;livesupport-src&gt;/modules/storageServer/var</code>
 directory </li>
   <li> <code>http://localhost:80/livesupportArchiveServer/</code>
-should point to the <code>&lt;livesupport-cvs&gt;/modules/archiveServer/var</code>
+should point to the <code>&lt;livesupport-src&gt;/modules/archiveServer/var</code>
 directory </li>
   <li> <code>http://localhost:80/admin/</code>
-should point to the <code>&lt;livesupport-cvs&gt;/modules/htmlUI/var</code>
+should point to the <code>&lt;livesupport-src&gt;/modules/htmlUI/var</code>
 directory </li>
 </ul>
-Please make <code>&lt;livesupport-cvs&gt;/modules/htmlUI/var/templates_c/</code>
+Please make <code>&lt;livesupport-src&gt;/modules/htmlUI/var/templates_c/</code>
 and
-<code>&lt;livesupport-cvs&gt;/modules/htmlUI/var/html/img/</code>
+<code>&lt;livesupport-src&gt;/modules/htmlUI/var/html/img/</code>
 writable for
 apache.
+
 <h3>Multiple developers doing development on the system</h3>
 In case multiple developers are sharing a system for LiveSupport
 development, each resource has to be personalized. Please run the <code>livesupport/bin/user_setup_db.sh</code>

livesupport/doc/release.html

@@ -54,7 +54,7 @@ control system</li>
 To get a fresh copy of the LiveSupport repository, execute the
 following in an empty directory:<br>
 <br>
-<pre><code>cvs -z3 -d :ext:&lt;username&gt;@netfinity-5.mdlf.org:/home/cvs checkout -P livesupport</code><br></pre>
+<pre><code>svn checkout svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/livesupport/trunk/livesupport</code><br></pre>
 <br>
 Where <code>&lt;username&gt;</code> is the user name for accessing the
 repository of the person making the release.<br>
@@ -90,7 +90,7 @@ manager is quite picky on the format of the changelog file. See <a
  href="http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog">section
 4.4</a> of the Debian Policy Manual for more details.<br>
 <br>
-Don't forget to commit the changes made to the changelog into the CVS
+Don't forget to commit the changes made to the changelog into Subversion
 before proceeding.<br>
 <h1>Creating release tarballs<br>
 </h1>
@@ -137,22 +137,20 @@ The above commands will result in the following debian packages:<br>
 <br>
 <pre><code>livesupport-libs_&lt;ls-version&gt;-1_&lt;arch&gt;.deb<br></code><code>livesupport-station_&lt;ls-version&gt;-1_&lt;arch&gt;.deb<br></code><code>livesupport-studio_&lt;ls-version&gt;-1_&lt;arch&gt;.deb</code><br></pre>
 <pre><code></code><code></code></pre>
+
 <h1>Tagging the sources</h1>
 After the tarballs have been tested, the release can be finalized. As a
 first step, the current state of the LiveSupport version control
 repository has to be tagged, so that the the very versions in the
 release can be retrieved at any later date. To tag the repository,
-issue the following command from the LiveSupport checked out source
-directory:<br>
+issue the following command:<br>
 <br>
-<pre><code>cvs tag livesupport_&lt;ls-version&gt;<br></code></pre>
+<pre><code>svn copy svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/livesupport/trunk/ \
+         svn+ssh://&lt;username&gt;@code.campware.org/home/svn/repo/livesupport/tags/livesupport-&lt;ls-version&gt;<br></code></pre>
 <br>
-This will tag the current state of the repository with the tag <code>livesupport_&lt;ls-version&gt;</code>,
-enabling later retrieval of this specific state. Please note that since
-CVS does not support dots (<code>'.'</code>) in tags, the dots in the
-version number are replaced by underscore (<code>'_'</code>) when
-tagging. Thus, <code>livesupport-0.9.1</code> is tagged as <code>livesupport-0_9_1</code>,
-for example.<br>
+This will tag the current state of the repository with the tag <code>livesupport-&lt;ls-version&gt;</code>,
+enabling later retrieval of this specific state.<br>
+
 <h1>Publishing the tarballs</h1>
 To make the release available to the public, the created tarballs have
 to be published. This is done by making the files accessible under the

livesupport/doc/userLocalizationInstructions.html

@@ -54,9 +54,11 @@ list</a>.</p>
 <p>
 <ul>
     <li>If editing an existing language: download the latest version of the
-        <a href="http://netfinity-5.mdlf.org/cgi-bin/viewcvs.cgi/livesupport/products/gLiveSupport/var/">language file</a>
-        (click on the revision number, not the file name);
-        <p>if adding a new language: download <a href="http://netfinity-5.mdlf.org/cgi-bin/viewcvs.cgi/*checkout*/livesupport/products/gLiveSupport/var/root.txt">the latest version of root.txt</a>;</li>
+        language file ??.txt or ??_??.txt from
+        <a href="http://code.campware.org/projects/livesupport/browser/trunk/livesupport/products/gLiveSupport/var/">this directory</a> (click on the file
+        name, scroll down to the bottom, right-click on Plain Text and choose
+        Save Target As or Save Link As, depending on your browser);
+        <p>if adding a new language: download <a href="http://code.campware.org/projects/livesupport/file/trunk/livesupport/products/gLiveSupport/var/root.txt?format=txt">the latest version of root.txt</a>;</li>
     <li>edit the texts between the "..."s;</li>
     <li>save it as a plain text file in UTF-8 encoding.
         Please do not send Word documents or files in other encodings.</li>