Software: CVS for developers.
Tomas Berndtsson

Here is some internal information for our developers, what procedure to take to put a project on our CVS server.

First of all you will need to install the cvs program on your machine. With it also comes texinfo pages, with instructions for all CVS commands, and examples for some. For the lazy developers (aren't we all?), here a quick instruction how to import your sources into our CVS.

First, if you haven't before, you need to login, using the login row described above, but using your real username instead of anonymous. You need to enter your password when prompted.

Then go to the top of your source tree for the project. There, you write (as one line):

cvs -d {username}@cvs.nocrew.org:/usr/local/cvsroot
 import {module-name} {vendor} initial
Where you change {username} into your username, {module-name} into the name of your project, and {vendor} into whatever you want. We typically use NoCrew, capitalization optional, as vendor. We always use lower case on the module name. Please do not use the CVS pserver, as it sends passwords uncrypted over the network.

CVS will now import all files it finds necessary into the CVS. It usually picks out the files well, and automatically skips .o, .a, executables, backup files and a few others. In case it imported too many, or too few files, you can remove or add the files afterwards.

Before you do that, or continue working on your project, you first need to get yourself a CVS version of the source tree. Therefore, go to a different place in your file system, and check out your project, using the checkout row described above. Again, change anonymous into your real username. Then you are ready to start working on your project again. When you are in your source tree, you don't need to specify the CVSROOT every time.

The main CVS commands for the developer:
cvs commit - check in your changes to the server.
cvs add - add a file to your module.
cvs remove - remove a file from your module.
cvs update - check out others changes from the server.

Also useful is:
cvs diff - create a diff file between your tree and the tree on the server.

And don't forget to create a webpage for the project. :)