Providing customized source code control with CVS
Providing customized source code control with CVS
You need to decide if you have a special place in the directory tree to put cvs, and if you wish to use Kerberos for authentication and encryption. I recommend leaving CVS in the normal place, and using methods other than Kerberos, so you will not normally need the compilation options.
It is usually easy to compile and install CVS on Unix. Unfortunately, there are problems that can come up, and it is beyond the scope of this web site to troubleshoot. Since most people will not be compiling their own CVS, and most who do compile their own will find it easy, this is unlikely to happen to any specific user. Note that this is very similar to how most open source software is compiled and installed.
1. Unpack What you have downloaded is probably a file ending with ".tar.gz" or ".tgz", indicating that this has been compressed for faster downloading with gzip after having numerous files packed into one with tar. To unpack these:
gunzip <file name> This may take a minute or so,
and will change the compressed file into another one.
tar xf <file name> This will usually run
fast, and will normally create a directory of the download contents.
Do everything else in that directory.
2. configure This is usually as simple as typing
in ./configure. There are options you might need to
use:
--prefix=<directory>, if you have a special
place for CVS.
--with-krb4=<directory>, if you are going to
use Kerberos 4 and it is not installed in /usr/kerberos. Kerberos
4 is obsolescent, so you would only use this for compatibility with
earlier software.
--enable-encryption enables support for encryption
over Kerberos, which you probably should do if using Kerberos in
the first place.
--disable-dependency-tracking is necessary to avoid
certain problems with certain BSD Unixes, and should not be used
unless the compilation fails.
This step will take several minutes, and print out a long list of what you have installed in libraries, details of how your C compiler works, and so forth.
If you ever want to return to this step, type make distclean
to clear out the results and start over.
3. make Type make. This will compile
all of the files and can take some time. If it doesn't seem to
finish correctly, there may be a problem with dependency tracking,
and you should start over again with
make distclean
./configure --disable-dependency-tracking
make
4. Install You need to do this as the root user,
so type su and enter the root password. Then you
type make install, and stop being the root user with
exit.
Next: Configuring CVS
All contents of these pages Copyright 2002 by David H. Thornley. Permission granted for verbatim copying and use within an organization.