Personal CVS Modules

If you would like to have your thorn arrangements, or associated Cactus tools, on our password protected CVS server for development or distribution, please contact cactusmaint@cactuscode.org.

We have two repositories for general use:

• arrangements for Cactus thorn arrangements
• packages for Cactus associated tools and libraries, for example visualization clients or tools, data format libraries.

New Modules

Please supply us with the following information:

1. Name for module
2. One sentence description of module
3. Name of contact person (this person should issue all adminstrative requests for changes to the module)
4. Email address of contact person
5. Would you like your arrangement/tool to be advertised on our web pages etc.
6. Initial information as detailed in the following section.

Administering Module

We don't have any automatic scripts at the moment for you to administer a module yourself. So if you would like permissions/information changed, please email cactusmaint@cactuscode.org, being sure to include the following information:

1. Module name
2. Any changes to the access rights for the module (that is, who can checkout from the module). Note that this can be public meaning that anyone is free to access your arrangement or tool ... this is encouraged!
3. Any changes to the commit rights for the module (that is, who can commit changes to the module). (This one can't be public!)
4. Any changes to who should get Email information messages following commits to the module.

CVS Accounts

We can only set access and commit rights for people who have a personal account on our CVS server. To apply for a personal CVS account we need to know your

1. Full name
2. Affiliation
3. Email address
4. Requested username

Using the CVS Repositories

We're assuming that you already know how to use CVS (if not look at the documentation available on the CVS homepage.), so here we just list a few basic points (we'll use the arrangements repository in the example, just replace arrangements with packages for the packages repository.):

Login

You need to do this only once for each machine you are using

cvs -d :pserver:<loginname>@cvs.cactuscode.org:/arrangements login
CVS password: <password>

First Import of Module

You should be located inside the directory you are importing. (Note that you need to checkout your module after importing it before any editing, to get a CVS checked out version).

cvs -d :pserver:<loginname>@cvs.cactuscode.org:/arrangements import \
	      -m "<import log message>" <your module name> start v1

Checkout of Module

cvs -d :pserver:<loginname>@cvs.cactuscode.org:/arrangements checkout \
	      <module name>

Update of Module

From inside your checked out module

cvs -d :pserver:<loginname>@cvs.cactuscode.org:/arrangements update