Information and hints on using CVS
-
The main CVS web page
has the manual for CVS.
-
Need to define the variables CVS_RSH and CVSROOT . Depending
on your shell, this can be done with the commands: setenv CVS_RSH ssh
; setenv CVSROOT username@cvs.jlab.org:/group/hallc/cvsroot
. It is probably useful to define the variables in your login script.
-
To initally check out the Analyzer CVS package follow these
directions.
-
The simplest way to keep the Analyzer package updated is
to issue the command : cvs update when in the Analyzer directory.
-
To interact with the CVS by the SSH you will always have
to enter your password unless you do a few things. The Jlab Compter center
has a web page
on SSH that explains how to setup your account so you do not have
to always enter a password . ( At least onsite, from reading their write-up
it seems not possible from offsite)
-
If you like the GUI approach instead of the command line
approach, then I would recommend using Tkcvs.
If you are onsite at you can copy the excutables /home/jones/bin/tkcvs
and /home/jones/bin/tkdiff . Remember
that Tkcvs or any cvs commands must be run in the directory
where the CVS files are located which in most cases means the Analyzer
directory.
-
Once you have checked out the Analyzer CVS package then you
need to keep it updated. To check if you need to update use
the command: cvs -n update . The -n is a flag that tells
cvs to execute the command but do nothing. This way you can see what cvs
would do. To update then issue the command:
cvs
update. If there are modified files on the CVS repository then
you will see a U by the filename . If you see a ?
next
to the filename that means that the file is not in the CVS repository.
After compiling the analyzer there are some files which get created which
are not in the CVS repository. Some types of these files are : the subdirectories
O.Linux
or O.Sunos which store the object and dependency files , the
r_*.f
files which are create from the common blocks so that parameters, test
and histograms are accessible through the CTP program.
This page is maintained by Mark Jones ( jones@jlab.org)
. Last updated Feb. 19 , 2003.