CVS.Terminator.Net
Information and guidelines for using the services at the Terminator CVS
server.
Notice
The Terminator CVS repository was recently moved to a new server, were
the setup is slightly different from the old one. There may still lay some
old information around refeering to the old server setup, if so please
report it to the cvs admin so it can be removed.
Also beware that the new setup is a bit more complex than the old one,
and not tested to well yet, so there may exist problems and also small
adjustments of the setup may occur - so check out this page for the most
recent information if something fails, and report any problems to the cvs
admin.
Introduction
This CVS server is configured to serve multiple CVSROOT's with independent
acess and user lists. Some of the CVSROOT's are available for public read
access, while others are for private use and therefor closed (and hidden)
from unautorized users.
Available roots
is providing development sources for most of the GPL licensed projects
developed and distributed by TerminatorNet.
ROOTNAME = terminator
is providing sources for the various tools and patches used on the XSW
Terminator XShipWars server. Please note that this repository is NOT
provided, approved or supported by the official XShipWars distributors,
so everything contained here is highly unofficial. We will still try to
keep a branch with copies of the official distribution updated.
ROOTNAME = xsw
CVS Browser
Most of the public available projects may be browsed from a webreader
using the CVSWEB system.
General cvs procedures
Here's some instructions on how to access the server from a local client,
using commandline.
Guest access (readonly)
User access (requires registration)
Docs
Some useful documents for understanding and using the CVS tools.
CVS Manual
CVS FAQ
CVS Quick Ref
Links
CVS homepage Main site for
the cvs system, with docs and downloads.
Common procedures
Guest access - readonly
(Run from the parent of the workfolder)
Checkout - download source with cvs info to local workfolder
cvs -d :pserver:guest@cvs.terminator.net:/vhome/cvs/root/<ROOTNAME>
checkout <MODULENAME>
Export - download clean source without cvs info to local folder
cvs -d :pserver:guest@cvs.terminator.net:/vhome/cvs/root/<ROOTNAME>
export <MODULENAME>
Update - update existing workfolder to the latest server revison
( Run from toplevel of the local workfolder )
cvs update
Developer access
Creating a new branch from workfolder
A.8.2.2 Creating the branch after editing
Say you have been working on some extremely experimental
software, based on whatever revision you happened to checkout
last week. If others in your group would like to work on this
software with you, but without disturbing main- line
development, you could commit your change to a new branch.
Others can then checkout your experimental stuff and utilize
the full benefit of CVS conflict resolution. The scenario might
look like:
[[ hacked sources are present ]]
$ cvs tag -b EXPR1
$ cvs update -r EXPR1
$ cvs commit