This document describes DPGP CVS archive procedures that can be used by individuals with an account on the DPGP central computing cluster. Please email Kristian Stevens (see contact list) if you have any questions about this documentation or your account status.

Preface

Once you have a user account virtually the entire library of cvs commands is available to you as a remote user through the ssh interface. The default format for a local cvs command is:

  cvs [ cvs_options ] cvs_command [ command_options ] [ command_args ]

A few additional steps are required to work remotely through ssh.

1. Find out where ssh is located.

         $ which ssh
         /usr/bin/ssh

2. Set the CVS_RSH environment variable

         $ export CVS_RSH=/usr/bin/ssh    # for bash users
         or
         $ setenv CVS_RSH /usr/bin/ssh    # for csh and tcsh users
   

3. when issuing cvs commands replace cvs with

         cvs -d :ext:yourusername@dpgp.org:/cvsroot
   

4. If it's the first time you have ssh'ed to dpgp.org you will be asked

         Are you sure you want to continue connecting (yes/no)?yes
   

5. Lastly you will be asked for your secret account pasword.

Checking Out the Latest Version

This is probably the most used command. If this is the first time for you to check out a project from the cvs you will probably want to organize your projects under a single directory. Once you have checked out a project it should be updated and maintained as opposed to checking out additional copies.

For instance if you would like to check out the latest version of RATools

      $ cd DPGPCVS
      $ cvs -d :ext:yourusername@dpgp.org:/cvsroot co RATools

Be sure to replace yourusername with your user name. This will create an RATools directory in which you can compile and edit the sourcecode.

Updating your Checked Out Copy

Possibly the second most utilized cvs command. This should always be done before embarking on editing the sourcecode as it may prevent synchronization issues with other users.

For instance if you would like to update your checked out version of RATools

      $ cd DPGPCVS/RATools
      $ cvs -d :ext:yourusername@dpgp.org:/cvsroot update

Making and Comitting Changes

Changes should be saved back to the archive only when they have been successfully compiled and tested. This ensures that the latest copy of the code is always a working copy.

Before making changes run the cvs update command. This will ensure that your local copy of the source code is up to date before you make changes.

You will also want to run cvs update again after you have made your changes. This will update any files that have changed during the time you have been working as well as notify you which files you changed. Fir instance if I edit the align_chip.c file

      $ cvs -d :ext:yourusername@dpgp.org:/cvsroot update
        cvs update: Updating .
        M align_chip.c

This is good. There are no concurrency issues and no other files have changed sp I can commit my changes back to the archive.

      $ cvs -d :ext:yourusername@dpgp.org:/cvsroot commit
        Checking in align_chip.c;

The cvs commit command will open up the vi editor for you to describe your changes. Write a few lines abou the changes you made. If you are not in insert mode press i. When you are finished exit insert mode with esc and then save with shift-ZZ.

Your changes have been committed.

        Checking in align_chip.c;
        /cvsroot/RATools/align_chip.c,v  <--  align_chip.c
        new revision: 1.14; previous revision: 1.13

Anonymous Access

The DPGP CVS repository is read accessible by anonymous cvs. Use the following protocol to obtain access to the CVS archive:

First, set the CVSROOT environment which variable contains the remote access information.

$ CVSROOT=:pserver:anonymous@x-dpgp.ucdavis.edu:/cvsroot
$ export CVSROOT

Then login with the password anonymous

 $ cvs login

Checking Out Projects

Checkout of a project, in this example RATools is done as follows:

$ cvs checkout RATools