CVS
This article is a stub. You can help by expanding it.
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.
Installation
USE flags
USE flags for dev-vcs/cvs Concurrent Versions System - source code revision control tools
crypt
|
Add support for encryption -- using mcrypt or gpg where applicable |
doc
|
Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally |
kerberos
|
Add kerberos support |
nls
|
Add Native Language Support (using gettextGNU locale utilities) |
pam
|
Add support for PAM (Pluggable Authentication Modules)DANGEROUS to arbitrarily flip |
server
|
Enable server support |
Emerge
Installing cvs is as easy as running an emerge command:
root #emerge --ask dev-vcs/cvs Note
If planning on using CVS for serving source code to clients be sure to emerge it with the
If planning on using CVS for serving source code to clients be sure to emerge it with the
server USE enabled!Configuration
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.
Usage
Checkout a CVS module by using the following command:
user $cvs checkout <module_name>More coming soon...
See also
- The CVS Tutorial article.
External resources
- The CVS man page locally (man cvs) or online at
- [gentoo-dev] Packages up for grabs: dev-vcs/cvs* (post CVS project disband)
This article is issued from Gentoo. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.