[GRASS-SVN] r31244 - grass-web/trunk/devel

svn_grass at osgeo.org svn_grass at osgeo.org
Sun May 4 16:44:21 EDT 2008 

Author: neteler
Date: 2008-05-04 16:44:20 -0400 (Sun, 04 May 2008)
New Revision: 31244

Modified:
   grass-web/trunk/devel/cvs.inc
Log:
reverted last change

Modified: grass-web/trunk/devel/cvs.inc
===================================================================
--- grass-web/trunk/devel/cvs.inc	2008-05-04 19:34:41 UTC (rev 31243)
+++ grass-web/trunk/devel/cvs.inc	2008-05-04 20:44:20 UTC (rev 31244)
@@ -1,33 +1,32 @@
 <!-- MN -->
 
-<a href="#what">What is SVN</a> - <a href="#intro">SVN and GRASS development</a> <br>
-- GRASS SVN Access: 
- [ <B><a href="http://trac.osgeo.org/grass/browser/grass/trunk/">Live Online Interface</a></B>
+<a href="#what">What is CVS</a> - <a href="#intro">CVS and GRASS development</a> <br>
+- GRASS CVS Access: 
+ [ <B><a href="http://freegis.org/cgi-bin/viewcvs.cgi/grass6/">Live Online Interface</a></B>
 - <a href="#access">Software</a>
 - <a href="#web">Website</a>
 <!-- merged into source code - <a href="#progman">ProgMan</a> --> ] <br>
-- <a href="#branches">SVN tags/branches</a>
-- <a href="#snapshots">SVN snapshots</a>
-- <a href="#commitML">SVN commit ML</a>
+- <a href="#branches">CVS tags/branches</a>
+- <a href="#snapshots">CVS snapshots</a>
+- <a href="#commitML">CVS commit ML</a>
 - <a href="#further">Further reading</a>
 
 <p>
-<a NAME="what"></a><h2>What is SVN?</h2>
+<a NAME="what"></a><h2>What is CVS?</h2>
 
-The Subversion system (SVN) provides network-transparent source
+The Concurrent Versions System (CVS) provides network-transparent source
 control for groups of developers. They can work independently and "feed the
 system" (the source code repository) remotely through internet - day and
-night from all over the world. Note, that the SVN write access is
-restricted to experienced developers. See <a href="http://trac.osgeo.org/grass/wiki/HowToContribute">here</a> how to
-request write access.
+night from all over the world. Note, that the CVS write access is
+restricted.
 
-<p>Even if you do not contribute to the code development, the SVN allows to
-follow development progress easily through the update function. After
-downloading the full GRASS SVN tree, just the future <b>changes</b> will be
-downloaded by using the SVN client software. This method reduces further downloads
+<p>Even if you do not contribute to the code development, the CVS allows to
+follow development progress easily through "anonymous-CVS". After
+downloading the full GRASS CVS tree, just the future <b>changes</b> will be
+downloaded by using the CVS software. This method reduces further downloads
 for updating your local GRASS sources extremely.
 
-<p>Further features of SVN:
+<p>Further features of CVS:
 
 <ul>
 <li>
@@ -48,76 +47,101 @@
 time</li>
 </ul>
 
-<a NAME="intro"></a><h2>SVN and GRASS development</h2>
+<a NAME="intro"></a><h2>CVS and GRASS development</h2>
 
-The usage of SVN prevents us and you from further GRASS version confusion. As every
-change is under control of the SVN system the current state as well as old
+The CVS prevents us and you from further GRASS version confusion. As every
+change is under control of the CVS system the current state as well as old
 versions can be accessed. This is very important for bug-tracking (finding
 bugs introduced by changes).
 
 <p>
-<a href="http://web.soccerlab.polymtl.ca/grass-evolution/cvs-stat/overall/index.html">SVN statistics for GRASS 6</a>
+<a href="http://web.soccerlab.polymtl.ca/grass-evolution/cvs-stat/overall/index.html">CVS statistics for GRASS 6</a>
 
-<p>If you download the GRASS sources from the SVN system, you will get the
-latest version available! Of course, you can also download a previous
-version, as you prefer. Once downloaded the entire GRASS SVN tree including
-the hidden SVN-internal subdirectories you can follow the ongoing development
-easily. The "svn update" function downloads only the changes not yet arrived
-on your local system. The SVN client software compares the GRASS source code
-version in the SVN-server with your local version.
+<p>If you download the GRASS sources from the CVS system, you will get the
+latest version existing! Of course, you can also download a previous
+version, if you prefer. Once downloaded the entire GRASS CVS tree including
+the CVS-internal subdirectories you can follow the ongoing development
+easily. The "cvs update" function downloads only the changes not yet arrived
+on your local system. The CVS software compares the GRASS source code
+version in the CVS-server with your local version.
 
-<p> The SVN software is freely distributed <a
-href="http://subversion.tigris.org/">here</a> and usually shipped within several
-Linux/MacOSX etc. distributions. It is available for rather every operating system.
+<p>As GRASS is a rather big package this might be one reason for you to use
+CVS. However, we recommend this only to experienced users who know how to
+compile software. The CVS software is freely distributed <a
+href="https://www.cvshome.org/">here</a> and usually shipped within several
+Linux distributions. It is available for rather every operating system.
 
-<p>The GRASS-SVN service is hosted at <a
-href="http://trac.osgeo.org/grass/wiki">OSGeo Foundation</a>, USA. There is
-a "web-SVN" interface which allows to browse the source code online.
+<p>The GRASS-CVS service is hosted at <a
+href="http://intevation.net">Intevation GmbH</a>, Germany. There is
+additionally a "web-cvs" interface which allows to browse the source code.
 The status of each file (its change history) is written there, you can also
 download individual files. Jump in and see how it is working!
 
-<p>The GRASS SVN version will be published from time to time as an official release.
+<p>The GRASS CVS version will be published from time to time as an official release.
 
 <p>
 <center><table BORDER NOSAVE >
 <tr BGCOLOR="#FFFFCC" NOSAVE>
 <td NOSAVE><a NAME="access"></a>
-<b>GRASS SVN repository access </b>(public read access)
+<b>GRASS CVS repository access </b>(public read access)
 
-Please see <a href="http://trac.osgeo.org/grass/wiki/DownloadSource">Downloading GRASS Source</a>, section
-"Subversion...".
+<ul>
+<li>
+  <tt>export CVSROOT=:pserver:grass-guest at intevation.de:/home/grass/grassrepository</tt>
+  <p>
+   Then do a "cvs login" and type "grass" when your are asked for password.<br>
+   Now you can checkout the tree using the command <br>
+   <tt>cvs -z3 co grass6</tt>
+<P>
+See more detailed <a href="http://freegis.org/grass/">GRASS-CVS access instructions</a> to
+access the anomymous CVS. Even more detailed instructions: <a
+href="../faq/cvs_howto.html">GRASS CVS access: step by step</a>
+<li><a href="http://freegis.org/cgi-bin/viewcvs.cgi/">CVS HTML web interface</a>
+   (browse the repository)
+<li><a href="http://freegis.org/grass/howto_grass-sshcvs.en.html">CVS write access
+for developers</a>
+</ul>
 
 <a NAME="branches"></a>
-<b>GRASS SVN tags and branches:</b>
+<b>GRASS CVS tags and branches:</b>
 <ul>
-<li><a href="cvstags.php">List of GRASS SVN tags and branches</a>
+<li><a href="cvstags.php">List of GRASS CVS tags and branches</a>
 </ul>
 
-<a NAME="snapshots"></a><b>GRASS SVN snapshots:</b>
+<a NAME="snapshots"></a><b>GRASS CVS snapshots:</b>
 
-If you are not familiar with SVN software, but want to get rather the latest
-GRASS code from SVN, we provide SVN snapshots. A SVN snapshot is the latest
-GRASS source code which is extracted from SVN on a weekly basis: Get the <a
-href="../grass63/source/snapshot/">weekly SVN-snapshot</a> in a .tar.gz package.
+If you are not familiar with CVS software, but want to get rather the latest
+GRASS code from CVS, we provide CVS snapshots. A CVS snapshot is the latest
+GRASS source code which is extracted from CVS on a weekly basis: Get the <a
+href="../grass60/source/snapshot/">weekly CVS-snapshot</a> in a .tar.gz package.
 <P>
 
-<a NAME="commitML"></a><b>SVN commits mailing list:</b>
-We have established a <a href="grasscvscommit.php">GRASS SVN commit
+<a NAME="commitML"></a><b>CVS commits mailing list:</b>
+We have established a <a href="grasscvscommit.php">GRASS CVS commit
 mailing list</a>. This mailing list distributes "commit messages" from the
-SVN system. After subscription you will receive a message about every
-change in GRASS SVN repository along with the related comment.
+CVS system. After subscription you will receive a message about every
+change in GRASS CVS repository along with the related comment.
 </td>
 </tr>
 
 <tr BGCOLOR="#CCFFFF" NOSAVE>
 <td NOSAVE><a NAME="web"></a>
-<b>Web site SVN management</b>
-<br>Developers have write access
-to maintain the GRASS web pages, see <a href="http://trac.osgeo.org/grass/wiki/WebPagesManagement">Web Pages Management</a>
-for details.
+<b>Web site CVS management</b> (developers only)
+<br>Developers have access
+to maintain the GRASS web pages:
+<dl>
+<dd>
+Set the CVSROOT variable (with
+your CVS ID)&nbsp;</dd>
 
+<dd>
+cvs -z3 co web&nbsp;</dd>
+
+<dd>
+</dd>
+
 <br>The web site is updated
-by a cronjob hourly. <br>
+by a cronjob four times a day. <br>
 Web pages management 
 <a href="http://lists.osgeo.org/mailman/listinfo/grass-web">mailing list</a>
 </dl>
@@ -126,12 +150,75 @@
 
 <tr BGCOLOR="#CCFFFF">
 <td><a NAME="progman"></a>
-<b>Programmer's manual SVN managment</b>
-<br>2004: The document was merged in doxygen style into the source code, just edit there.
+<b>Programmer's manual CVS managment</b> (developers only)
+<br>2004: The document was merged in doxygen style into the source code.
 </td>
 </tr>
 </table></center>
 
+<p>
+<a NAME="further"></a>Further
+introductional texts to CVS:
+
+<ul>
+
+<li>What is a branch: <a href="http://www.loria.fr/~molli/cvs/doc/cvs_5.html">General
+  information about branches in CVS</a>
+
+<li>
+<a href="http://www.tldp.org/HOWTO/Software-Release-Practice-HOWTO/patching.html">Good
+patching practice</a> (part of <a href="http://www.tldp.org/HOWTO/Software-Release-Practice-HOWTO/index.html">Software Release Practice HOWTO</a>)
+
+<li>
+<a href="http://cvsbook.red-bean.com/">The
+CVS Book</a> with online chapters by Karl Fogel</li>
+
+<li>
+<a href="http://dev.zope.org/CVS/ZopeCVSFAQ">ZopeCVSFAQ</a>
+ - recommended reading for CVS and branches</li>
+
+<li>
+<a href="http://durak.org/cvswebsites/doc/">CVS--Concurrent
+Versions System</a> by Sean Dreilinger</li>
+
+<li>
+<a href="http://ximbiot.com/cvs/cvshome/cyclic/cvs/doc-blandy.html">CVS
+training material</a> by Jim Blandy</li>
+
+<li>
+<a href="http://www.devguy.com/fp/cfgmgmt/cvs/">CVS Help and Information</a>
+by DevGuy</li>
+</ul>
+
+
+Download the binary CVS client program:
+
+<ul>
+<li>
+<a href="https://www.cvshome.org">CVS
+software</a>, here is the <a href="https://www.cvshome.org/downloads.html">Download
+site</a></li>
+
+<li>
+Linux CVS client binaries:
+please check your Linux distro...</li>
+
+<li>
+CVS on <a href="https://www.cvshome.org/dev/codes.html">other
+clients: Windows, Mac, BeOS, ...</a></li>
+
+<li>
+JAVA based client: <a href="http://www.jcvs.org">jCVS</a></li>
+
+<li>
+Tcl/TK based client: <a href="http://www.twobarleycorns.net/tkcvs.html">TkCVS</a></li>
+
+<li>
+Windows users: Do not use winCVS
+as the file transfers won't be done correctly. Please use <a href="https://www.cvshome.org/dev/codewindow.html">cygwin
+cvs</a> or other software.</li>
+</ul>
+
 <div align="right">
 <i>Last change: $Date$ </i><br>
 <i>$Author$</i>

More information about the grass-commit mailing list