New CVS release from Cyclic Software

1 files changed, 31 insertions, 31 deletions

diff --git a/gnu/usr.bin/cvs/INSTALL b/gnu/usr.bin/cvs/INSTALL
index 335fbf949ba..4907134c6c5 100644
--- a/gnu/usr.bin/cvs/INSTALL
+++ b/gnu/usr.bin/cvs/INSTALL
@@ -5,16 +5,19 @@ First, read the README file.  If you're still happy...
 CVS has been tested on the following platforms.  The most recent
 version of CVS reported to have been tested is indicated, but more
 recent versions of CVS probably will work too.  Please send updates to
-this list to info-cvs@prep.ai.mit.edu.
+this list to bug-cvs@prep.ai.mit.edu (doing so in the form of a diff
+to this file is encouraged).
 
 Alpha:
 	DEC Alpha running OSF/1 version 1.3 using cc (about 1.4A2)
 	DEC Alpha running OSF/1 version 2.0 (1.4.90)
 	DEC Alpha running OSF/1 version 2.1 (about 1.4A2)
 	DEC Alpha running OSF/1 version 3.0 (1.5.95) (footnote 7)
+	DEC Alpha running OSF/1 version 3.2 (1.7+obvious patch)
 HPPA:
 	HP 9000/710 running HP-UX 8.07A using gcc (about 1.4A2)
 	HP 9000/715 running HP-UX 9.01 (1.6)
+	HPPA running HP-UX 10.01 (1.7)
         HPPA 1.1 running HP-UX A.09.03 (1.5.95) (footnote 8)
         HPPA 1.1 running HP-UX A.09.04 (1.7.1)
 	NextSTEP 3.3 (1.6.86)
@@ -26,13 +29,17 @@ i386 family:
 	BSDI 2.0 (1.4.93) (footnote 5)
 	FreeBSD 2.0.5, i486, gcc (1.5.95)
 	NextSTEP 3.3 (1.6.86)
+	NeXTSTEP 3.3 (1.7), (footnote 10)
 	SCO Unix 3.2.4.2 (1.4.93) (footnote 4)
 	SCO OpenServer 5.0.0, "CC='cc -b elf' configure"
 	Lynx 2.3.0 080695 (1.6.86) (footnote 9)
-	Windows NT 3.51 (1.6.86 client-only)
+	Windows NT 3.51 (1.7.87 client-only)
+	QNX 4 (1.7 + obvious patches)
+	OS/2 Version 3 using IBM C/C++ Tools 2.01 (1.7.86 with patches)
 m68k:
 	Sun 3 running SunOS 4.1.1_U1 w/ bundled K&R /usr/5bin/cc (1.6)
 	NextSTEP 3.3 (1.6.86)
+	NeXTSTEP 3.3 (1.7), (footnote 10)
 	Lynx 2.3.0 062695 (1.6.86) (footnote 9)
 m88k:
 	Data General AViiON running dgux 5.4R2.10 (1.5)
@@ -42,12 +49,12 @@ MIPS:
 	DECstation running Ultrix 4.2a (1.4.90)
 	DECstation running Ultrix 4.3 (1.6.86)
 	SGI running Irix 4.0.5H using gcc and cc (about 1.4A2) (footnote 2)
-	SGI running Irix 5.3 (1.4.93)
+	SGI running Irix 5.3 (1.7)
 	SGI running Irix-6 (about 1.4.90) (footnote 3)
 	Siemens-Nixdorf RM600 running SINIX-Y (1.6)
 PowerPC or RS/6000:
 	IBM RS/6000 running AIX 3.1 using gcc and cc (1.6.86)
-	IBM RS/6000 running AIX 3.2.5 using xlc (1.5)
+	IBM RS/6000 running AIX 3.2.5 (1.7.87)
 	IBM RS/6000 running AIX 4.1 using gcc and cc (about 1.4A2) (footnote 1)
 	Lynx 2.3.1 120495 (1.6.86) (footnote 9)
 SPARC:
@@ -56,6 +63,7 @@ SPARC:
 	Sun SPARCstation running Solaris 2.4 using gcc and cc (about 1.5.91)
 	Sun SPARC running Solaris 2.5 (2.5 beta?) (1.6.4)
 	NextSTEP 3.3 (1.6.86)
+	NeXTSTEP 3.3 (1.7), (footnote 10)
 
 (footnote 1)
 	AIX 4.1 systems fail to run "configure" due to bugs in their
@@ -100,6 +108,12 @@ SPARC:
     So after running configure I had to undef HAVE_DIRENT_H and
     define HAVE_SYS_DIR_H.
 
+(footnote 10) Ralf E. Stranzenbach <ralf@reswi.ruhr.de>
+    I've made some modifications to "filesubr.c" to deal with NFS
+    mounted directories (and those funny .nfs* files). This patch
+    should be used whenever the programmers "sandbox" is located on
+    a NFS mounted device --- at least on NeXTSTEP.
+
 -------------------------------------------------------------------------------
 
 Installation under Unix:
@@ -117,7 +131,7 @@ Installation under Unix:
     value is "/usr/local", with binaries in sub-directory "bin", manual
     pages in sub-directory "man", and libraries in sub-directory "lib".
 
-    This release of CVS also requires RCS commands to be installed in
+    If you are using server or local CVS, RCS needs to be installed in
     the user's PATH (or a path you have configured in src/options.h,
     or a path specified with the -b option).  If you don't have RCS,
     you will need to get it from GNU as well.  It is best to get the
@@ -211,9 +225,11 @@ Installation under Unix:
     If you receive any un-expected output from the regression tests,
     it may indicate a bug in CVS (or might just indicate a problem
     running the tests).  If you choose to submit a bug report,
-    relevant information to include might be your "config.status"
-    file, your host type, operating system and compiler information,
-    the contents of check.log, and any "make check" output.
+    be aware that, as with all bug reports, you may or may not get a
+    response, and your odds might be better if you include enough information
+    to reproduce the bug, an analysis of what is going wrong (if you have
+    the time and ability to provide one), etc.  The check.log file is the
+    first place to look.
 
 4)  Install the binaries/documentation:
 
@@ -234,24 +250,10 @@ Installation under Unix:
     possibly be made to fit your environment).  If things look good,
     continue on...
 
-6)  Setup the master source repository.  Choose a directory with ample disk
-    space available for source files.  This is where the RCS ",v" files
-    will be stored.  Note that this should be some shared directory for your
-    site.  It should probably be auto-mounted, if you're running NFS.
-
-    Say you choose "/src/master" as the root of your source repository.
-    Run the "cvsinit" script to help you set it up.  It will ask you to
-    enter the path to your CVSROOT area.  You would enter /src/master in
-    this example.
-
-	$ ./cvsinit
-
-    The cvsinit script will setup a reasonable CVSROOT area to start with.
-    It is also valuable to folks who already have a CVSROOT area setup from
-    using earlier releases of CVS.  It assumes that you have installed CVS
-    already (step 4) and that the RCS programs (co and ci) are in your
-    PATH.  There are many ways to customize CVS for your site.  Read the
-    cvs(5) manual page when you get the chance.
+6)  Set up the master source repository.  See the "Setting up the repository"
+    section of cvs.texinfo for details; the one-line summary is (if you
+    are putting the repository in /src/master):
+    $ cvs -d /src/master init
 
 7)  Have all users of the CVS system set the CVSROOT environment
     variable appropriately to reflect the placement of your source
@@ -277,7 +279,7 @@ Installation under Unix:
     following commands:
 
 	$ make distclean
-	$ cvs import -m 'CVS 1.6 distribution' cvs CVS CVS-1_6
+	$ cvs import -m 'CVS 1.6 distribution' cvs CVS_DIST CVS-1_6
 
 9)  Having done step 8, one should be able to checkout a fresh copy of the
     CVS distribution and hack away at the sources with the following command:
@@ -288,10 +290,8 @@ Installation under Unix:
     This will make the directory "cvs" in your current directory and
     populate it with the appropriate CVS files and directories.
 
-10) Remember to edit the modules file manually when sources are checked in
-    with "cvs import" or "cvs add".  A copy of the modules file for editing
-    can usually be retrieved with the "cvs checkout modules" command, and
-    definitely with the "cvs checkout CVSROOT" command.  See cvs(5).
+10) You may wish to customize the various administrative files, in particular
+    modules.  See cvs.texinfo for details.
 
 11) Read the NEWS file to see what's new.