Getting and Installing CVS

Windows              Unix                Browsing the Code

Click on to return to start of page

Introduction

If you are unfamiliar with CVS you can find out more about the utility here. CVS . 

If you want a quick guide to the most commonly used CVS commands you can take look at Joanne's CVS Quick Help page right here. CVS Quick Help

Instructions for Windows 

1. Download and install WinCvs from www.wincvs.org.  Go to the WinCVS section of the downloads link from the main page and choose the latest version which looks stable. Do not choose the one which has the shared object libraries. 

    If there are problems contact  Richard.  Two points to consider:

• The WinCvs program is needed only for command-line cvs executable.  You are free to use the gui if you desire, but it is not necessary for accessing the repository (nor will we explain how it should be used).

2. Add the location where you installed WinCVS (which contains the cvs executable) to your PATH environment variable.

1. Windows 2000 / XP
   open   Start --> Settings --> Control Panel --> System
   choose Advanced --> Environment Variables

2. Windows NT
   Start->Settings->Control Panel->System->Environment

3. CVSROOT is used to specify to CVS which computer and where on that computer the repository is located.

    Set an environment variable CVSROOT to be

    :ext:centaurusa.slac.stanford.edu:/nfs/slac/g/glast/ground/cvs
   [:ext:centaurusa.slac.stanford.edu:/nfs/slac/g/glast/flight/archive]

i.e. in csh based shell (e.g. tcsh) use the following command:

setenv CVSROOT: ext: centaurusa.slac.stanford.edu: nfs/slac/g/glast/ground/cvs

and in sh based shell (e.g. bash) use the following command:

CVSROOT =":ext: centaurusa.slac.stanford.edu: nfs/slac/g/glast/ground/cvs"; export CVSROOT

Make sure that you don't have a space at the end of you CVSROOT environment variable.

NOTE: If your account name on your local machine differs from your SLAC account name, you need to prepend your account name to the noric node name, as in  

:ext:richard@centaurusa.slac.stanford.edu:/nfs/slac/g/glast/ground/cvs

4. CVS_RSH specifies the protocol with which to logon.

    Set an environment variable CVS_RSH to be ssh

Another reminder about the environment variables to edit 

Instructions for Unix 

1. CVSROOT is used to specify to cvs which computer and where on that computer the repository is located.  CVS_RSH specifies the protocol with which to logon.

    Set an environment variable CVSROOT to be

    :ext:centaurusa.slac.stanford.edu:/nfs/slac/g/glast/ground/cvs

    [:ext:centaurusa.slac.stanford.edu:/nfs/slac/g/glast/flight/archive]

If your account name on your local machine differs from your SLAC account name, you need to prepend your account name to the noric node name, as in 

        :ext:richard@centaurusa.slac.stanford.edu:/nfs/slac/g/glast/ground/cvs

Make sure that you don't have a space at the end of your CVSROOT environment variable.

        i.e. in csh based shell (e.g. tcsh) use the command:

setenv CVSROOT /nfs/slac/g/glast/ground/cvs 

and in sh based shell (e.g.bash) use the command:

CVSROOT ="/nfs/slac/g/glast/ground/cvs"; export CVSROOT  

 

2. CVS_RSH specifies the protocol with which to logon.

    Set an environment variable CVS_RSH to be ssh

        i.e. in csh based shell (e.g. tcsh) use the command:

        setenv CVS_RSH ssh

        and in sh based shell (e.g.bash) use the command:

        CVS_RSH="ssh"; export CVS_RSH

Notes to Linux Users External To SLAC

Currently there are some difficulties with Kerberos authentication at SLAC. This will cause some garbage in the output stream when doing CMT checkouts. SLAC Computing Services is aware of the problem. The error message will look something like this:

Warning: Kerberos authentication disabled in SUID client.
/usr/X11R6/bin/xauth: creating new authority file /tmp/Xauth6801_14059

Browsing the Code  

You can browse the code  and view the various packages via cvsweb 

You can see all our packages in the long list to the left. Most of the packages with names in all caps, like XMLEXT, are interface packages. They don't actually contain any code; they are just a means to defining appropriate symbols so that our code can find external (imported) libraries and associated include files. 

Packages whose names start with "Gaudi" are part of the Gaudi framework, really another external library but treated somewhat specially. Almost all the rest contain code written for GLAST. Browse around to get a feel for typical organizations (there is more than one) for these packages, keeping an eye on the "age" column for the file ChangeLog, which is automatically updated whenever anyone makes a change to the package. Any package which hasn't been updated in the last few months is probably not of much interest. Most packages have at least the following subdirectories

• src Contains all private source: all implementation files, normally with suffix .cxx, and those header files which are private to the package, normally with suffix .h. Should also contain a special documentation file called mainpage.h which gives an overview of the package purpose and contents.
• packagename The subdirectory with the same name as the package contains public header files
• doc Should contain a special documentation file called release.notes.
• cmt or, in older packages, mgr This special directory is used by CMT to keep track of the configuration needed to build a package. The requirements file is the tool the developer has to tell CMT what symbols are needed, what to build, etc. Another important file in this directory, derived from the requirements file by CMT, is called setup.sh (use setup.csh instead for csh or tcsh). It defines symbols needed to build the package, to build other packages dependent on it, and to run applications using the package.

Last Modified January 21, 2003

Back to Main Menu        Previous Step        Next Step