SeedCvs

UserPreferences

See the WinCvsWithSeed page for setting up a Windows machine to check out SEED code.

To check out a clean copy of code from CVS and use it within a working SEED install use the following commands.

For bash:

cd FIGdisk 
source config/fig-user-env.sh 
cd dist/releases 
mkdir myworkdir 
cd myworkdir 
export CVS_RSH=ssh 
cvs -d :ext:username@biocvs.mcs.anl.gov:/disks/cvs/bio co seed_base 
cp ReleaseTools/Makefile.top Makefile 
switch_to_release myworkdir 

And for csh/tcsh:

cd FIGdisk 
source config/fig-user-env.csh 
cd dist/releases 
mkdir myworkdir 
cd myworkdir 
setenv CVS_RSH ssh 
cvs -d :ext:username@biocvs.mcs.anl.gov:/disks/cvs/bio co seed_base 
cp ReleaseTools/Makefile.top Makefile 
switch_to_release myworkdir 

It is important to have sourced the fig-user-env script any time you wish to run a make, as the make process relies upon environment settings in that script.

In order to do updates of the whole tree from the work directory, you'll need to set an environment variable. For bash:

export CVSROOT=:ext:username@biocvs.mcs.anl.gov:/disks/cvs/bio 

and for csh/tcsh:

setenv CVSROOT :ext:username@biocvs.mcs.anl.gov:/disks/cvs/bio 

Say you're working on the main FIG module. You might do this:

cd FigKernelPackages 
edit FIG.pm 

To make the changes take effect, you need to run a make command in your work directory:

cd myworkdir 
make 

At some point you may want to commit your changes to the repository. You need to ensure that you are up to date with the repository, then commit the changes:

cvs update 
cvs commit -m "a comment about this commit" FIG.pm 

If you leave off the -m, an editor will be brought up for you to type your comment into.