Concurrent Versions System
|Developer(s)||The CVS Team|
|Initial release||November 19, 1990|
1.11.23 / May 8, 2008
1.12.13 / July 26, 2006
|Operating system||Unix-like, Windows|
|License||GNU General Public License|
CVS operates as a front end to Revision Control System (RCS), an older version control system that manages individual files but not whole projects. It expands upon RCS by adding support for repository-level change tracking, and a client-server model. Files are tracked using the same history format as in RCS, with a hidden directory containing a corresponding history file for each file in the repository.
CVS uses delta compression for efficient storage of different versions of the same file. This works well with large text files with few changes from one version to the next. This is usually the case for source code files. On the other hand, when CVS is told to store a file as binary, it will keep each individual version on the server. This is typically used for non-text files such as executable images where it is difficult to create compact deltas between versions.
CVS excludes symbolic links because when they are stored in a version control system they can pose a security risk. For instance, a symbolic link to a sensitive file can be stored in the repository, making the sensitive file accessible even when it is not checked in. In place of symbolic links, scripts that require certain privileges and conscious intervention to execute may be checked into CVS.
CVS labels a single project (set of related files) that it manages as a module. A CVS server stores the modules it manages in its repository. Programmers acquire copies of modules by checking out. The checked-out files serve as a working copy, sandbox or workspace. Changes to the working copy are reflected in the repository by committing them. To update is to acquire or merge the changes in the repository with the working copy.
CVS uses a client–server architecture: a server stores the current version(s) of a project and its history, and clients connect to the server in order to "check out" a complete copy of the project, work on this copy and then later "check in" their changes. CVS servers can allow "anonymous read access", wherein clients may check out and compare versions with either a blank or simple published password (e.g., "anoncvs"); only the check-in of changes requires a personal account and password in these scenarios. Several developers may work on the same project concurrently, each one editing files within their own "working copy" of the project, and sending (or checking in) their modifications to the server. To avoid conflicts, the server only accepts changes made to the most recent version of a file. Developers are therefore expected to keep their working copy up-to-date by incorporating other people's changes on a regular basis. This task is mostly handled automatically by the CVS client, requiring manual intervention only when an edit conflict arises between a checked-in modification and the yet-unchecked local version of a file. Clients can also use the "update" command to bring their local copies up-to-date with the newest version on the server. Clients can also compare versions, request a complete history of changes, or check out a historical snapshot of the project (e.g.: based on a given date). If the check in operation succeeds, then the version numbers of all files involved automatically increment, and the server writes a user-supplied description line, the date and the author's name to its log files. CVS can also run external, user-specified log processing scripts following each commit. These scripts are installed by an entry in CVS's
loginfo file, which can trigger email notification or convert the log data into a Web-based format.
CVS can also maintain different "branches" of a project. For instance, a released version of the software project may form one branch, used for bug fixes, while a version under current development, with major changes and new features, can form a separate branch. CVS assumes that the majority of work takes place on the trunk, and that branches should generally be short-lived or historical. When used as designed, branches are easily managed and branch operations are efficient and fast.
I created CVS to be able to cooperate with my students, Erik Baalbergen and Maarten Waage, on the ACK (Amsterdam Compiler Kit) C compiler. The three of us had vastly different schedules (one student was a steady 9-5 worker, the other was irregular, and I could work on the project only in the evenings). Their project ran from July 1984 to August 1985. CVS was initially called cmt, for the obvious reason that it allowed us to commit versions independently.
Grune publicly released the code on June 23, 1986.
The code that eventually evolved into the current version of CVS started with Brian Berliner in April 1989, with later input from Jeff Polk and many other contributors. Brian Berliner wrote a paper introducing his improvements to the CVS program—which describes how the tool was extended and used internally by Prisma, a third-party developer working on the SunOS kernel, and was released for the benefit of the community under the GPL. On November 19, 1990, CVS version 1.0 was submitted to the Free Software Foundation for development and distribution.
The latest version was released on 8 May 2008.
Adoption and successors
In the world of open source software, the Concurrent Version System (CVS) has long been the tool of choice for version control. And rightly so. CVS itself is free software, and its non-restrictive modus operandi and support for networked operation—which allow dozens of geographically dispersed programmers to share their work—fits the collaborative nature of the open-source world very well. CVS and its semi-chaotic development model have become cornerstones of open-source.
Over time, developers have created new version control systems based on CVS in order to add features, alter the operational model, and improve developers' productivity. CVS replacement projects include CVSNT and Subversion.
- "CVS--Concurrent Versions System v22.214.171.124: Overview". Archived from the original on 15 April 2012. Retrieved 9 December 2011.
- Stopak, Jacob (November 30, 2019). "The Evolution of Version Control System (VCS) Internals". Retrieved 22 September 2020.
- Charles D. Cranor; Theo de Raadt (1999). "Opening The Source Repository With Anonymous CVS, USENIX 1999" (PDF).
- Collins-Sussman, Ben; Greg Ward (September 2004). "Subversion Users: Re: Performance (Subversion vs. CVS)". subversion-users. Retrieved 2010-07-07.
- West, Adrian (July 2004). "cvs branchtag performance fix". Archived from the original on 2009-08-03. Retrieved 2010-07-07.
- "Concurrent Versions System CVS". dickgrune.com.
- Dick Grune (July 3, 1986). "CVS, an RCS front-end (cvs)". Newsgroup: mod.sources. Usenet: 122@mirror.UUCP. Retrieved September 14, 2016.
- "CVS II: Parallelizing Software Development - Berliner (ResearchIndex)". Archived from the original on September 9, 2004.
- "[cvs] Contents of /ccvs/NEWS". cvs.savannah.gnu.org.
- "Concurrent Versions System - News: Stable CVS Version 1.11.23 Released! [Savannah]". savannah.nongnu.org.
- Ben Collins-Sussman, Version Control with Subversion For Subversion 1.1, 2005
- "Subversion FAQ: Why does this project exist?". Subversion. Retrieved September 21, 2009.
- "Dispelling Subversion FUD". Ben Collins-Sussman. Archived from the original on July 18, 2011. Retrieved June 30, 2010.
- David Thomas; Andrew Hunt (2003). Pragmatic Version Control Using CVS. The Pragmatic Programmers. ISBN 0-9745140-0-4.
- Jennifer Vesperman (2006). Essential CVS (2e ed.). O'Reilly. ISBN 0-596-52703-9.
- Per Cederqvist; et al. Version Management with CVS. ISBN 0-9541617-1-8. Archived from the original on 2014-08-05. Retrieved 2009-11-25.
- Karl Franz Fogel; Moshe Bar. Open Source Development with CVS. ISBN 1-932111-81-6. Archived from the original on 2014-07-16. Retrieved 2002-02-05.