Remove CVS access to repository.

[Tyson Richard DOWD]

We've got a few groups who are going to need access to the CVS archive
in the near future, so I've written this quick guide to how to use CVS
in client server mode.

The servers are up and running, so if you'd like to test-drive this
documentation, feel free, and let me know how it goes. We'll probably 
need to add entries to hosts.allow for any outside sites we want to
allow access to.

Any comments?

If this is ok, I might add this to the repository somewhere so we can
send it to people who need access.

==========

How to use CVS client server to remotely access the Mercury CVS archive.

You need:
	- A version of CVS with client server support (1.9 works fine)
	  installed at the remote end. Probably anything older than
	  1.5 will work OK.

	- A TCP/IP connection to the internet.

First:
	- The CVS server uses password authentication. You need to
	  have a password installed in CVS's password file on
	  the server end.

	- Generate a password using standard UNIX /etc/passwd style
	  passwords. *Do not* use your normal password. A good way to
	  do this is change your password to something, copy the line
	  from /etc/password, then change it back. Only the username and
	  encrypted password are needed.

	  e.g. trd:s9FOR1a8DOxDs

	  (Shadow password will probably mess this up - mail us if
	  there's a problem).

	- Send this line to the Mercury team, who will install it for you.
	  If you have local access to the CVS repository, you can just
	  add it to /home/staff/zs/imp/CVSROOT/passwd

	- Access via Windows or other non-UNIX platforms is untested,
	  but theoretically possible.

Then (once you've been added to the passwd file):

	- set your CVSROOT environment variable to

	  username at mercury.cs.mu.oz.au:/home/staff/zs/imp
or
	  username at hydra.cs.mu.oz.au:/home/staff/zs/imp

	(we have two because sometimes one of the machines is down - 
	it doesn't matter much which one you use).

	- run "cvs login" to login to the server for the first time.

	- cvs will remember your password from now on (it's rather
	  insecurely stored in a slightly jumbled manner in ~/.cvspass),
	  so you rarely have to login again.

	- you can do "cvs co mercury" to check out the main mercury
	  module. This can take a while over a slow connection, but you
	  should see pretty steady progress messages, eg
	  	U mercury/.INSTALL.in
		U mercury/.README.in
		U mercury/.cvsignore
		U mercury/BUGS
		U mercury/COPYING
		U mercury/COPYING.LIB
		etc

	- Other CVS modules of interest are
	  	tests		- test cases for the compiler
		clpr		- the clpr interface
		www		- the www page

NOTE:
	- Developers should subscribe to the mercury-developers mailing
	  list, to keep up-to-date on development discussion, and 
	  to be able to participate in discussions about code they
	  want to change. This is a forum to ask questions about how
	  to change something, discuss design trade-offs, and report
	  on any development that you suspect will influence others.
	  (traffic is moderately high in this mailing list - between
	  100 and 300 messages per month, you should filter it if
	  possible).

	- Before committing any code, read the policy on reviews for the
	  Mercury system (mercury/compiler/notes/reviews.html or 
	  http://www.cs.mu.oz.au/research/mercury/developer/reviews.html).
	  Basically, we don't commit broken code into the repository,
	  and we don't commit unreviewed code.


-- 
       Tyson Dowd           #          Another great idea from the 
                            #            people who brought you
      trd at .cs.mu.oz.au      #               Beer Milkshakes!
http://www.cs.mu.oz.au/~trd #	         Confidence --- Red Dwarf