Some fast notes:

Installing CVS and RCS

• Got CVS and RCS from ftp://prep.ai.mit.edu; relatively straightforward compile under Irix 6.2 with gcc.
  • CVS version 1.9
  • RCS version 5.7
• Modified automount maps so that /usr/local/cvsroot is mounted automatically on all machines. Source directory is mounted from spot/export/9gig/localMounts/cvsroot.
• Modified /etc/services and /etc/inetd.conf on the server machine, pinafore.stl.nps.navy.mil, to start up CVS pserver automatically on connects. This is covered on p. 19, section 4.6.2 of the CVS manual.
• Initialized the repository by running command

  cvs -d /usr/local/cvsroot init

  . This creates the directory CVSROOT under /usr/local/cvsroot. Covered on page 17 on the manual, section 4.5.
• Set owner equal to the user cvs, and group membership equal to the new group cvs. Added all the users that will be using cvs to the cvs group.
  • This is actually overly broad. There should be a group for each project under cvs control; eg, djv, npsnet, cap, and so on. This gives you finer grained control, so that npsnet doesn't have change control over djv. Each module directory under cvsroot would have different group ownership.
• You can, optionally, add a passwd file to CVSROOT to allow for remote logins with different passwords and effective users. Create a passwd file of the format cvsUsername:encryptedPassword:effectiveUsername and place it in the CVSROOT directory, eg: testuser:46hLKUa/MFVOE:mcgredo. This allows someone to use (say) jCVS to log into the server, supply the username testuser and the password, and operate on the server machine with the priviliges of the unix user mcgredo. Presumably mcgredo belongs to the group that has access to the directories in question, eg cvs.
• Checked in the sources. This is covered on page 23, section 5.1.1 of the manual. Created directory tree inside of /usr/local/cvsroot, eg mil/navy/nps; cd'd to directory with the source in it; and checked in the entire directory with

  cvs import -m "Initial sources" mil/navy/nps/dis djv start

  . This checks in the directory, makes entries in CVSROOT, and creates the ,v files.
• Only the java files and assorted text files are under cvs control. The javadocs can be generated from the java files, as can the class files. Binary files can be supported by cvs, if you so desire.

jCVS

Installing jCVS

• Get the sources from www.ice.com/java/jcvs/index.shtml.
• Start up the application by starting a dos or terminal window, cd'ing to the application directory, then firing it up with

  java
  -classpath ./jcvs.jar;c:/jdk1.2.2/lib/classes.zip CVSApplication

  .  The application itself lives in the jar file, and the classes.zip file is where all the jdk distribution classes live.

Using jCVS

• Check out sources by selecting File-> Checkout. This brings up a dialog box. Select Pserver, Use Password. Use your usual username and password for the unix server box. The CVS module is the subdirectory under cvsroot on the server you want to check out, for example mil/navy/nps/dis. CVS server is the unix server that runs the pserver (the one with the modifications to inetd.conf you set up earlier.) The cvs repository is /usr/local/cvsroot. The local directory is where you want the checked out source to reside, eg c:\djv.
• You'll get a text window that displays any errors, and a project window that displays all the checked out filenames and version numbers.
• Edit the files to your heart's content.
• When finished, select "commit" from the project menu. jCVS will search the directory for modified files and update the sources on the server. You'll get a window that prompts you for comments on your changes.
• You can view the log file associated with a file by highlighting the file in the project window, then choosing selection-> show log. This displays all the comments added in the checkout process above.
• You can apply "tags" to a series of files, logically grouping together perhaps several file version numbers on different files into one release. Suppose you want a build with release 1.1 of ActionRequestPdu.java and version 1.2 of NetworkMonitor. The most up-to-date versions of these are 1.4 and 1.5, respectively. You'd check out the correct versions from cvs, select all the files you want to apply the tag to (probably everything in the directory), then enter a text tag in the text field at the top of the checkout/project window. (You can't use some characters in the tag, such as $, ., and a few others.) Pick Selection-> Tag Files. This will apply the tag to the files on the server repository.
• To check out an earlier version on the project, from the main opening window select "checkout". The checkout parameters window comes up. Supply the usual information, but in the "arguments" field supply something like "-r tagName". This will check out all files that have had that tag applied. By default, the initial checkin supplied a tag of "start" to all files, so you can checkout the original version of the module (including any files that may have been deleted from the module.)
• You can check out sources without the CVS administrative directories by using the cvs export command.
• To import a new module, to file-> import from the main window. Use /usr/local/cvsroot as the repository, pinafore.stl.nps.navy.mil as the server, and the directory name under cvsroot (minus a leading /) as the module name. Use "djv" as the owner name and "start" as the initial tag.