[GRASSweb-list]markus: web/faq cvs_howto.html,1.8,1.9

[grass at intevation.de]

Author: markus

Update of /grassrepository/web/faq
In directory doto:/tmp/cvs-serv28768

Modified Files:
	cvs_howto.html 
Log Message:
cosmetics

Index: cvs_howto.html
===================================================================
RCS file: /grassrepository/web/faq/cvs_howto.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- cvs_howto.html	4 Feb 2005 15:42:51 -0000	1.8
+++ cvs_howto.html	26 Oct 2005 10:10:03 -0000	1.9
@@ -21,21 +21,21 @@
 on obtaining source for other versions:
 <ol>
 <li>
-To reduce download time, get
-the weekly <a href="../grass60/source/snapshot/">CVS snapshot</a>. It contains
-the entire sources including the CVS subdirectories which you need to synchronize
-this package with CVS.</li>
+To reduce download time, either get
+<li> the weekly <a href="../grass60/source/snapshot/">6.0-CVS snapshot</a> (stable), or,
+<li> the weekly <a href="../grass61/source/snapshot/">6.1-CVS snapshot</a> (development, more advanced).
+</ul>
+
+The snapshot contains the entire sources including the CVS subdirectories which you need to
+synchronize later again with CVS for updates.</li>
 
 <li>
-Extract this package as described
-<a href="../grass60/source/README.html">here</a>
-(it is the README from the source directory). The full sources of the GRASS
-Project require about 100 MB.</li>
+Extract this package as described in the README from the source directory. The full
+sources of the GRASS Project require about 60 MB.</li>
 
 <li>
-After extracting the sources,
-you have to login into the CVS. To set up your CVS client for read access
-simply set the environment variable CVSROOT to:<br>
+After extracting the sources, you have to login into the CVS. To set up your CVS client
+for read access, simply set the environment variable CVSROOT to:<br>
 <br>
 <tt>:pserver:grass-guest at intevation.de:/home/grass/grassrepository</tt><br>
 <BR></li>
@@ -56,31 +56,24 @@
 when you are asked for password (note: your system will remember this
 next time).
 <li>
-Now update the snapshot (as
-new code may have arrived): By invoking<br>
+Now update the snapshot (as code updates may be available): By invoking<br>
 <BR></li>
 
 &nbsp;<tt>cvs up -dP</tt>
 <BR>
-<br>&nbsp;the GRASS version
-on your machine is compared to the CVS version. Only new files will be
-transfered. This CVS command will update your GRASS source code. Note:
-This is rather fast and will take maybe 10-15min. depending on your modem
-speed.
+<br>&nbsp;the local GRASS code on your machine is compared to that of the CVS server.
+Only new files will be transfered. This CVS command will update your GRASS source code. Note:
+This is rather fast and will take maybe 5-15min. depending on your modem/network speed.
 <li>
-To compile, see the local INSTALL
-file (even for code optimization).</li>
+To compile, see the local INSTALL file (even for code optimization or compilation of
+single modules).</li>
 </ol>
 
 <h3>Updating the GRASS code later on:</h3>
-<p>GRASS 6-CVS: The snapshot has to be transmitted
-once only. For future updates simply run the following command within the main GRASS
-source directory:
-<br><tt>&nbsp;&nbsp; cvs up
--dP</tt>
-<br>This will update your source
-code again. You can also just update a subdirectory: cd to this directory
-and use above command.
+<p>NOTE: The snapshot has to be transmitted only a single time. For future updates
+ simply run the following command within the main GRASS source directory:
+<br><tt>&nbsp;&nbsp; cvs up -dP</tt>
+<br>This will update your source code again (and again and...).
 <P>
 
 <p>Enjoy ongoing GRASS development!
@@ -91,3 +84,4 @@
 
 </body>
 </html>
+