Providing customized source code control with CVS
Providing customized source code control with CVS
There are no real decisions to make here. If you are going to use a Windows server, you need CVSNT. If you choose this, download the latest Windows executable from there, install it where you want it, and go on to configuring CVS. If not, continue on.
If you are using Unix, you should get a download from the official site, CVSHome, this being the current download page. This page provides pointers to the source code, and binaries for several different systems.
You probably want the latest version that's been out for more than a week or so. Theoretically, the "major versions" (like 1.10 and 1.11) get better quality control than the "minor versions" (like 1.11.1), but I don't think this matters in practical terms. CVS is mature software, and so the latest available version is probably the best. Since bugs have crept into release versions, I recommend waiting a week or so to see if any have cropped up. New releases get extensive use (and therefore testing) immediately upon becoming available.
If there is a binary version available for your platform in the
version you want, take it. If it is for Red Hat Linux, it
can be installed with rpm --install <filename>,
and otherwise it will be the "cvs" program, which can simply be
installed in /usr/local/bin.
If you aren't going to use a binary distribution, because the one you want isn't available, it isn't difficult to build from source. You need standard Unix development tools, which should be provided in your Unix distribution.
All contents of these pages Copyright 2002 by David H. Thornley.