From: Nicholas Nethercote <njn@valgrind.org>
Date: Mon, 21 Jul 2003 10:17:58 +0000 (+0000)
Subject: Added instructions on checking out from SourceForge CVS to the README file.
X-Git-Tag: svn/VALGRIND_2_0_0~18
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fea2973bd218096ae6e3cb3d7cc00bb15a700381;p=thirdparty%2Fvalgrind.git

Added instructions on checking out from SourceForge CVS to the README file.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1769
---

diff --git a/README b/README
index d696d1c0c2..42175a7e6b 100644
--- a/README
+++ b/README
@@ -68,25 +68,29 @@ docs/techdocs.html.
 
 Building and installing it
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
-If you install from CVS :
+To install from CVS :
 
-  0. cd into the source directory
+  0. Check out the code from CVS, following the instructions at
+     http://sourceforge.net/cvs/?group_id=46268.  The 'modulename' is
+     "valgrind".
 
-  1. Run ./autogen.sh to setup the environment (you need the standard
-     autoconf tools to do so)
+  1. cd into the source directory.
 
-If you install from a tar.gz archive:
+  2. Run ./autogen.sh to setup the environment (you need the standard
+     autoconf tools to do so).
 
-  2. Run ./configure, with some options if you wish. The standard
+To install from a tar.gz archive:
+
+  3. Run ./configure, with some options if you wish. The standard
      options are documented in the INSTALL file.  The only interesting
-     one is the usual --prefix=/where/you/want/it/installed
+     one is the usual --prefix=/where/you/want/it/installed.
 
-  3. Do "make"
+  4. Do "make".
 
-  4. Do "make install", possibly as root if the destination permissions
+  5. Do "make install", possibly as root if the destination permissions
      require that.
 
-  5. See if it works.  Try "valgrind ls -l".  Either this works,
+  6. See if it works.  Try "valgrind ls -l".  Either this works,
      or it bombs out complaining it can't find argc/argv/envp.
      In that case, mail me a bug report.