From: asherman@laser.fmrco.com (Aaron Sherman)
Subject: Re: gnu CVS help wanted
Reply-To: asherman@fmrco.COM
Organization: I-Kinetics, 19 Bishop-Allen Dr., Cambridge, MA
Date: Sun, 26 Jul 1992 23:59:56 GMT


>>>>> riepe@z.eecs.umich.edu (Michael Anthony Riepe) said:

riepe> I am looking for someone who is willing to give me some help in using
riepe> GNU cvs.  Please reply by e-mail, I doubt this is of general interest.

This has been asked (and answered via Email) enough times to warrent a
post.

riepe> CVS seems ideal for my needs - I have an application that I
riepe> would like to put under RCS control.  Its source is made up of a large
riepe> directory hierarchy, and CVS seems like a good way to simplify the 
riepe> archive system.  Unfortunately, I have been unable to create the
riepe> initial CVS source repository, and would appreciate some help from
riepe> someone who has used it before (none of the unix support counselors
riepe> here at UM have ever even *heard* of CVS).

You need the "cvsinit" script which lives in the root of the source
tree. This script lives in the top-level of the cvs 1.3 source tree.
There are also docs about it in the "INSTALL" file.

riepe> The man page seems fairly complete in its discussion of the use of RCS
riepe> on an existing source repository, but is not helpful at all in the
riepe> process of creating the repository to begin with (Brian
riepe> Berliner [author] are you listening?). 

Here are diffs to follow for the man-page and Makefile, so that
information about cvsinit will be easier to find, and cvsinit will get
installed when you install cvs (this is not the best way to do all of
this. cvsinit should live in src, and be installed with the rest of
the programs. Brian is making the assumption that cvsinit will only be
run once, by the installer of CVS. This is only true if there is ONLY
ONE repository on each system, which may not be the case for various
reasons):

--- Makefile.in.orig    Sun Jul 26 18:34:37 1992
+++ Makefile.in Sun Jul 26 18:37:45 1992
@@ -121,9 +121,12 @@
 clean-info:
 install-info:

-install:
+install: install-cvsinit
        @for dir in $(SUBDIRS); do echo making $@ in $$dir; cd $$dir; $(MAKE) $(MDEFINES) $@ || exit 1; cd ..; done
 .PHONY: install
+
+install-cvsinit: cvsinit
+       $(INSTALL) cvsinit $(bindir)/cvsinit

 tags:
        @for dir in $(TSUBDIRS); do echo making $@ in $$dir; cd $$dir; $(MAKE) $(MDEFINES) $@ || exit 1; cd ..; done

--- man/cvs.1.orig	Thu Apr  9 23:05:16 1992
+++ man/cvs.1	Sun Jul 26 18:53:51 1992
@@ -50,6 +50,9 @@
 This copy is called the source ``repository''; it contains all the
 information to permit extracting previous software releases at any
 time based on either a symbolic revision tag, or a date in the past.
+.SP
+Note: if you are creating a \fInew\fP source repository with \fBcvs\fP,
+then you will want to see the \fIGETTING STARTED\fP section, below.
 .SH "ESSENTIAL COMMANDS"
 .B cvs
 provides a rich variety of commands (\fIcvs_command\fP in the
@@ -1810,6 +1813,34 @@
 \fB\-l\fP, \fB\-P\fP, \fB\-p\fP, \fB\-Q\fP, \fB\-q\fP, and \fB\-r\fP
 are also available with \fBupdate\fP.
 .RE
+.SH "GETTING STARTED"
+To create a \fInew\fP \fBcvs\fP source repository (note, this is not for
+adding a new tree to an existing repository):
+.LP
+Setup the master source repository.  Choose a directory with ample disk
+space available for source files.  This is where the \fBRCS\fP ",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 \fBNFS\fP.
+.LP
+Say you choose "/src/master" as the root of your source repository.
+Run the \fBcvsinit\fP script to help you set it up.  It will ask you to
+enter the path to your \fICVSROOT\fP area.  You would enter /src/master in
+this example.
+.SP
+.RS 5
+$ cvsinit
+.RE
+.SP
+The \fBcvsinit\fP script will setup a reasonable \fICVSROOT\fP area to
+start with.
+It is also valuable to folks who already have a \fICVSROOT\fP area setup
+from
+using earlier releases of \fBCVS\fP.  It assumes that you have installed
+\fBCVS\fP
+already and that the \fBRCS\fP programs (co and ci) are in your
+\fIPATH\fP.  There are many ways to customize \fBCVS\fP for your site.
+Read the
+\fBcvs(5)\fP manual page when you get the chance.
 .SH "FILES"
 For more detailed information on
 .B cvs
--
--------
Disclaimer: I am solely responsible for the content of this message.
The views expressed here may not be the views of I-Kinetics, Fidelity,
any of the Fidelity-owned corporations or my mother.