Instructions for use of Yale CVS Repository
This page provides basic information, advice, and hints for using the SML/NJ CVS repository at Yale.
Repository address
flint.cs.yale.edu:/home/cvs
Mailing list
There is a mailing list, smlnj-cvs@rum.cs.yale.edu, that will automatically receive messages announcing commits to the repository. To join the mailing list, send mail to smlnj-cvs-request@rum.cs.yale.edu with subject:
subscribe <your@email.address>
Setting up and using ssh
- To get access: send Stefan Monnier your public SSH-1 key along with a set of machine names (full domain paths) from which you'll login. Here is how you can generate an SSH-1 key and transmit it to Stefan:
% ssh-keygen % Mail -s "here you are" monnier@cs.yale.edu <~/.ssh/identity.pubssh-keygenwill ask you to enter a passphrase, which you'll need to remember and use whenever you use the Yale repository.You can check whether your access is authorized by executing
ssh -v flint.cs.yale.edu
- set CVS_RSH
export CVS_RSH=ssh
- use ssh-agent to set up for cvs usage. ssh-agent produces three lines of shell commands that should be evaled
eval `ssh-agent`- use ssh-add to authenticate for the whole session. ssh-add adds identity from ~/.ssh. Using this command, you won't be asked for authentication on each cvs command.
Here is a script that can be "sourced" to do all these steps:
export CVS_RSH=ssh export CVSROOT=flint.cs.yale.edu:/home/cvs eval `ssh-agent` ssh-add <<EOF <insert your passphrase here> EOFNote that if you have your DISPLAY variable set, the ssh-add ignores its standard input and pops up a dialog box into which you must type your passphrase.
CVS Hints
- Typical command:
cvs -d flint.cs.yale.edu:/home/cvs co smlnj
- To avoid having to specify the repository in each command, you can set CVSROOT:
export CVSROOT=flint.cs.yale.edu:/home/cvs
- It is recommended to have a ~/.cvsrc file containing
% cat ~/.cvsrc update -P -d checkout -P %The -P tells CVS to prune empty directories. The -d tells CVS to add new directories that have been created in the repository since the last update.
- When using `cvs import' it's useful to first try a dry run `cvs -n import' so you can fix the -I options (i.e. what files to ignore) or any other problems. Note that symbolic links are ignored by import. The global -n option for cvs suppresses any action and only generates reports of what the command would do.
Advice on Managing Branches
See Matthias's page with notes on managing private development branches.Also, see this follow-up advice on branching from Stefan.
Reminder: Tag all of smlnj module when committing
Matthias Blume, 31 Mar 2000
This is a reminder to everybody who is checking stuff into the CVS repository that they should tag the _entire_ repository (actually -- the entiry "smlnj" module if what you are doing is compiler-related). Otherwise tags are much less useful.
In this case I wanted to compare my "blume_main_v110p26p2_0" with the version _before_ that. For this, I tried to use the previous tag -- which was created by Alan. However, as it turns out, Alan tagged only those files he actually changed. As a result, CVS gave me only those files.
In other words, if a file does not have a certain tag, then it is considered non-existent. There is a flag to "cvs update" that lets one change this behavior to "use the most recent version", but this is also not what I wanted.
The other "solution" would be to really always tag "before" and "after" a commit. My point is that "before" tags are completely redundant if "after" tags are properly applied to the entire repository.
My current workaround is to use dates. (This proved a bit tricky because it wasn't obvious from the outset relative to which timezone the date would be interpreted... :)
Anonymous CVS
Stefan Monnier, 7 Apr 2000
I have a tentative setup for anonymous CVS working on rum (aka flint). To try it out, do the following:
% cvs -d :pserver:cvsguest@flint.cs.yale.edu:/guest login passwd: cvs % cvs -d :pserver:cvsguest@flint.cs.yale.edu:/guest co smlnj