CVS for Project 1

• the architecture we have written for you is under the directory project1_base/,
• under the directory project1/, we have allocated for each group a directory called 422g$/, where $ the group number (for example 422g1).

Step 1 **   Create a directory in your account.   For example, type:

mkdir   ~/422/

This directory is your working root.   It does not have to be ~/422/.   You decide yourself where to put your working root, and what name to give it.

Step 2 **   Go to the working root:

cd   ~/422/

Step 3 **   Type:

setenv   CVSROOT   /cs/classes/cis422/S01/CVSARCHIVE/

Step 4 **   Get the architecture from the CVS repository as follows:

cvs   checkout   project1_base

This will create a directory named project1_base under your working root.

Step 5 **   You also need to get the structure of your CVS group directory as follows:

cvs   checkout   project1/422g$

where $ is replaced by your group number (for example, project1/422g1).   This will create a hierarchical directory named project1/422g$ under your working root.   We will call this directory project1/422g$ the working directory.

There is no need to perform this installation more than once for the entire life cycle of the project 1, unless you delete your entire working root (we don't see why you want to erase it, anyway).

Every time you log in.

Step login-1 **   Perform Step 3.
Step login-2 **   Type:

cd   ~/working-root-path/project1/422g$

where working-root-path is the one you created in Step 1, and $ is replaced by your group number (for example, 422g1).

Edit, Create, Modify, etc.

Add new files.

Step add-1 **   You must be in your working directory.

Step add-2 **   Type:

cvs   add   the_new_file.java

Step add-3 **   Type:

cvs   commit   -m   "a short comment"   the_new_file.java

You should add to your CVS group's directory only those Java files that compile and run alright, although this is not checked by CVS.   The reason is to avoid any confusion among your group members who may check out files later.   If you cannot finish your task in one login session, you may leave things the way they are without doing any CVS adding.   You can logout.   Then, next time, just login, go to your working directory, and resume your task.   There may, however, be some reasons why you want to check in uncompiled codes.   That's ok as long as this does not create too much confusion.

Checkout the project.

Step checkout-1 **   You must be in your working root (the one you created in Step 1), and not in your working directory (the one you need to be in to edit files).

Step checkout-2 **   Type:

cvs   checkout   project1/422g$

where $ is replaced by your group number.

Step checkout-3 **   Go to your working directory project1/422g$

Update files.

Step update-1 **   Type:

cvs   commit   -m   "a short comment"   Kasparov.java

You should not place an updated file to your CVS group's directory unless it compiles and runs fine. The reason is explained in the NOTE above.

Removing files.

Step remove-1 **   If you want to rename it, use the mv command.   If you want to delete it, do it with the rm command.   In all cases remember its former name.   Let's say, the former name is old_code.java.

Step remove-2 **   Tell CVS that you really want to delete the file from your repository:

cvs   remove   old_code.java

Step remove-3 **   Perform the actual removal:

cvs   commit   old_code.java