A Quick Guide to Using CVS - Concurrent Versions System

Clif has suggested that we start to work with a ``professional'' code file management system so that we can easily share files. This system is called CVS, and Clif has prepared a basic set of instructions. Please try this. (Perhaps on Tuesday evening.)

Configuring your account to access CVS for this project

Modify your .login to

• include /home/flynt/bin in your search path,
• define the CVSROOT as /home/flynt/CVS_ROOT

That is, add these lines to the end of your .login:

setenv PATH $PATH\:/home/flynt/bin   
setenv CVSROOT /home/flynt/CVS_ROOT

Using CVS for CS 152

(1) To check out the code for the CS 152 art show project:

cvs checkout Project

This will create a new directory "Project", and will check out the most current revisions of all the files.

(2) To update your project directory to the checked in version:

  
cd Project
cvs update [filename]

If you include the optional filename, only that file will be updated (or marked as changed.) Without the filename, all files in the current directory are checked.

This will copy the most current version of the source code files into your directory.

If you've modified a file, it will mark that file to be copied to the repository.

If you've modified a file, and a new version has been checked into the repository, cvs will attempt to merge the changes into your file.

(3) To check your new code into cvs:

cd Project
cvs update [filename]
cvs commit [filename]

If you include the optional filename, only that file will be updated (or marked as changed.) Without the filename, all files in the current directory are checked.

You will be given an editor session to enter comments about the new code you are checking in.

(4) To add new source code files

cd Project
cvs add NewFile.java

History

• Created by Clif Flynt on Sunday, May 2, 1999.
• Formatted by Sam Rebelsky on Monday, May 3, 1999.