Super-K makes use of CVS to share and manage code between multiple users. The source code for the SK libraries (as well as various other documents and file) all lives in a cvs repository. The code can be "checked out" of the repository, and then compiled and run on various operating systems. Modified code can be checked back in for others to use. CVS keeps track of different modifications from different users, and can merge them appropriately.
ssh-keygen -t dsaDo not enter a password. This will create a file called id_dsa.pub in your ~/.ssh subdirectory. This is your ssh public key. Email this file to someone with access so it can be added to the authorized_keys2 file.
setenv CVS_RSH ssh setenv CVS_SERVER "env LOGNAME=squid cvs" setenv CVSROOT ":ext:skrep@kmcvs.icrr.u-tokyo.ac.jp:/home/skrep/repository"if squid is your username. The CVS_RSH variable tells it to use ssh for access, which is required. The CVS_SERVER variable gives it a log name for it to use for commits -- set this to your userid as shown above. The CVSROOT variable tells it where the repository lives.
You'll probably want to put these in your .tcshrc file.
The CVS manual gives full information on how to use cvs, but here a few useful commands:
cvs checkout modulename
cvs commit -m "Comment on what the change was" filename(Always, always give comments for your changes!)
cvs diff -rHEAD filename