CVS (Concurrent Versions System) is an important component of Source Configuration Management (SCM). Using CVS enables users to record the history of sources files and documents. It fills a similar role to the free software RCS, PRCS, and Aegis packages.
USE flags for dev-vcs/cvs Concurrent Versions System - source code revision control tools
||Add support for encryption -- using mcrypt or gpg where applicable|
||Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally|
||Build and install gtk-doc based developer documentation for dev-util/devhelp, IDE and offline use|
||Add kerberos support|
||Add Native Language Support (using gettext - GNU locale utilities)|
||Add support for PAM (Pluggable Authentication Modules) - DANGEROUS to arbitrarily flip|
||Enable server support|
Installing cvs is as easy as running an emerge command:
emerge --ask dev-vcs/cvs
If planning on using CVS for serving source code to clients be sure to emerge it with the
The default configuration file for CVS should be located in a file called ~/.cvsrc the user's home directory. Currently installing dev-vcs/cvs through Portage does not create a default configuration file, therefore any specific configuration must be done by the user.
Checkout a CVS module by using the following command:
cvs checkout <module_name>
More coming soon...
- The CVS Tutorial article.
- The CVS man page locally (man cvs) or online at
- [gentoo-dev] Packages up for grabs: dev-vcs/cvs* (post CVS project disband)