setenv EDITOR /cs/bin/pico # or your favorite text editor here
setenv CVSROOT /course/cs190/uml/cvs
setenv CVSREAD yes
This will set up what cvs needs to know to set up the cvs directories in your home directory. Re-login to your account and goto your home directory (or wherever you would like to keep _your_ local copy of the source tree) and type in:
cvs checkout uml
If all goes well, you should now see the uml directory in your current directory. Try opening the test.txt file in the uml directory in a text editor. If you can read the message, the install was a success. You can also test out and experiment with this file to get used to using cvs. For instance, to lock the file for editing and make the file writable, type:
cvs edit test.txt
when you're in the uml directory. Then edit the file and save it. Finally, type in:
cvs commit test.txt
It will now open the editor defined in the EDITOR environment variable for
you to put in a description of the changes to the file. Save the file and
quit the editor in order to finish the commit process. Your changes should
now be visible for everyone to see. Every time you start a session, you
should checkout the base uml directory to get any updates that have been
commited to the cvs source tree. You may have to checkout files again in
the same session if someone else updates his or her copy of a module. But,
if you have the file in edit mode (by using cvs edit) then no one else can
edit the file at the same time, and should re-checkout the file or module
when the other person is done with it. So, make sure that once you are
finished with a module or file, you commit the changes. If you want to
revert the file and release the lock because you do not like the changes,
type cvs unedit
cvs release uml
This will tell you if there are any uncommitted changes and will allow you
to commit the changes, revert the file, or leave the file be. But all
files will then be unlocked so that others can edit them. If you want to
play around with things, you can try adding the checkout line to your
.login and the release line to your .logout to automate the process, but I
don't trust automatic login scripts for much other than setting environment
variables, so I don't recommend it unless you really know what you are
doing. If you have any questions about the layout, or there is a problem
with the cvs system, feel free to email me.
-----------------
Chris