discuss: new documents ready for review
Subject:
Re: new documents ready for review
From:
Mysidia ####@####.####
Date:
8 Jun 2004 09:25:17 -0000
Message-Id: <20040608052958.A1439@i-55.com>
> > export ####@####.#### cvs -d $CVSROOT login
> D'oh!! This is actually two separate lines. I'll need to fix the markup to
> reflect this in the Author Guide.
Well, drop the leading 'export' and the command would be valid, but awkward.
...the point of CVS using a CVSROOT environment variable is a convenience to avoid
needing to use the -d option at all... And it seems redundant to both set the CVSROOT
environment variable _and_ use the -d option for the same value, all at once
(the -d parameter overrides the value of CVSROOT).
Using an environment variable (well, for bourne shell):
export ####@####.####
cvs login
or for C shell/tcsh:
setenv CVSROOT ####@####.####
cvs login
--
For the sake of generality (i.e. if someone uses a different shell than you think, or they
already have CVSROOT set for something else) the best notation to use, IMO is just one
line with -d: per command to setup a working directory
cvs -d ####@####.#### login
cvs -d ####@####.#### co (module name)
[And again the -d option for doing the check out. Of course CVS commands like
ci/tag/update/add/rm that are run with a working directory get the info they need
from CVS/Root and CVS/Repository and shouldn't normally need either -d or a CVSROOT
variable]
-Mysid
