Update (mainly concerning CVS use).

git-svn-id: svn://scm.gforge.inria.fr/svn/mpfr/trunk@2003 280ebfd0-de03-0410-8827-d642c229c3f4

2 files changed, 29 insertions, 15 deletions

diff --git a/README b/README
index 1b1288aa9..1325a2950 100644
--- a/README
+++ b/README
@@ -18,6 +18,7 @@ the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
 
 
 The MPFR distribution contains the following files:
+(This does not apply to code retrieved by CVS.)
 
 AUTHORS     - the authors of the library
 BUGS        - bugs in MPFR - please read this file!
@@ -46,3 +47,10 @@ mpfr.info   - info file for MPFR
 mpfr.texi   - texinfo documentation for MPFR
 tests/      - test directory
 texinfo.tex - TeX macros to handle mpfr.texi
+
+
+You can get the latest source code by CVS:
+
+  cvs -d :pserver:cvs@cvs-sop.inria.fr:/CVS/spaces checkout mpfr
+
+(empty password). CVS users should read the file "README.dev".
diff --git a/README.dev b/README.dev
index 5bb6aab05..1ca31e563 100644
--- a/README.dev
+++ b/README.dev
@@ -1,12 +1,30 @@
-Notes for the MPFR developers
-=============================
+Notes for the MPFR developers and CVS users
+===========================================
+
+To compile source code obtained from CVS, you need some GNU development
+utilities: aclocal, autoheader, automake, autoconf. As some files like
+"configure" are not part of the CVS repository, you first need to run
+the "prepare" script; you can give the same options as you would give
+to "configure" (give "--help" if you don't know).
+
+To generate mpfr.info, you need texinfo version 4.2 (or higher).
 
 The VERSION file contains the number of the next release version, i.e.
 the version currently developed. If nightly snapshots are built, the
 date in the yyyymmdd format must be added to the version number, for
 instance: "2.0.1-20020319".
 
-To make a release:
+When submitting patches, unified diffs (option -u) are recommended,
+as they are more readable. You can also use the option -d to generate
+a smaller set of changes. See diff(1) for more information.
+
+Though the ISO C standard requires that <stdlib.h> defines NULL,
+do not use NULL with #include <stdlib.h> only, because this will
+not work with the native SunOS 4 C compiler, whose headers are
+not conform to the standard (even with C90); other problems may
+occur on this architecture.
+
+To make a release (for the MPFR team):
   1) Check the version and update the date in mpfr.texi.
   2) Update the ChangeLog file (using a recent version of rcs2log,
      directly or with emacs), e.g. rcs2log > ChangeLog.2 and edit
@@ -20,15 +38,3 @@ To make a release:
      are replaced by dashes): cvs tag mpfr-2-0-1-rel
   6) Update the VERSION file to indicate the next version.
      Update the version in mpfr.texi.
-
-When submitting patches, unified diffs (option -u) are recommended,
-as they are more readable. You can also use the option -d to generate
-a smaller set of changes. See diff(1) for more information.
-
-Though the ISO C standard requires that <stdlib.h> defines NULL,
-do not use NULL with #include <stdlib.h> only, because this will
-not work with the native SunOS 4 C compiler, whose headers are
-not conform to the standard (even with C90); other problems may
-occur on this architecture.
-
-To generate mpfr.info, you need texinfo version 4.2 (or higher).