Revision Control System
This article's lead section may be too short to adequately summarize the key points. (September 2020) |
| Revision Control System | |
|---|---|
| Original author | Walter F. Tichy |
| Developer | GNU Project |
| Initial release | 1982 |
| Repository |
|
| Written in | C |
| Engine | |
| Operating system | Unix-like, V[1] |
| Type | Version control |
| License | GPL-3.0-or-later[a][2] |
| OpenRCS | |
|---|---|
| Original authors | Jean-Francois Brousseau, Joris Vink, Niall O'Higgins, and Xavier Santolaria |
| Developer | OpenBSD |
| Initial release | 2006 |
| Repository | cvsweb |
| Written in | C |
| Engine | |
| Operating system | OpenBSD |
| Type | Version control |
| License | BSD |
| Website | cvsweb |
Revision Control System (RCS) is an early implementation of a version control system (VCS). It is a set of UNIX commands that allow multiple users to develop and maintain program code or documents. With RCS, users can make their own revisions of a document, commit changes, and merge them. RCS was originally developed for programs but is also useful for text documents or configuration files that are frequently revised.[3]
History
[edit | edit source]Development
[edit | edit source]RCS was first released in 1982[3] by Walter F. Tichy at Purdue University. It was an alternative tool to the then-popular Source Code Control System (SCCS) which was nearly the first version control software tool (developed in 1972 by early Unix developers).[4] RCS is currently maintained by the GNU Project.[5]
An innovation in RCS is the adoption of reverse deltas. Instead of storing every revision in a file like SCCS does with interleaved deltas, RCS stores a set of edit instructions to go back to an earlier version of the file. Tichy claims that it is faster for most cases because the recent revisions are used more often.[3]
Legal and licensing
[edit | edit source]Initially (through version 3, which was distributed in 4.3BSD), its license prohibited redistribution without written permission from Walter Tichy:[6]
Copyright (C) 1982 by Walter F. Tichy [...] All rights reserved. No part of this software may be sold or distributed in any form or by any means without the prior written permission of the author.
A READ_ME file accompanied some versions of RCS which further restricted distribution, e.g., in 4.3BSD-Reno.[7]
Ca. 1989, the RCS license was altered to something similar to the contemporary BSD licenses, as seen by comments in the source code.[8]
Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by Walter Tichy.
RCS 4.3, released 26 July 1990, was distributed "under license by the Free Software Foundation", under the terms of the GPL.[9][full citation needed]
OpenBSD provides a different implementation called OpenRCS, which is BSD-licensed.[10]
Behavior
[edit | edit source]Mode of operation
[edit | edit source]RCS works well with standalone files and supports multi-file projects but, by modern standards, that support is limited: RCS can assemble the versions of multiple files into a single release (via "symbolic names")[11] but it lacks support for atomic commit across those files. Although it provides branching, the version syntax is cumbersome.[citation needed] Instead of using branches, many teams just use the built-in locking mechanism and work on a single head branch.[3]
Usage
[edit | edit source]RCS revolves around the usage of "revision groups" or sets of files that have been checked-in via the co (checkout) and ci (check-in) commands. By default, a checked-in file is removed and replaced with a ",v" file (so foo.rb when checked in becomes foo.rb,v) which can then be checked out by anyone with access to the revision group. RCS files (again, files with the extension ",v") reflect the main file with additional metadata on its first lines. Once checked in, RCS stores revisions in a tree structure that can be followed so that a user can revert a file to a previous form if necessary.[3]
Advantages
[edit | edit source]- Simple structure and easy to work with [12]
- Revision saving is not dependent on a central repository [12]
Disadvantages
[edit | edit source]- There is little security, in the sense that the version history can be edited by the users.[12]
- Only one user can work on a file at a time.[13]
Notes
[edit | edit source]- ^ GPL-3.0-or-later since 2010-06-24.
See also
[edit | edit source]- Concurrent Versions System (CVS)
- Apache Subversion (SVN)
References
[edit | edit source]- ^ V-System 6.0 Reference Manual
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ a b c d e Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).[dead ftp link] (To view documents see Help:FTP)
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).[dead ftp link] (To view documents see Help:FTP)
- ^ RCS 4.3 README file.
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ F. Tichy, Walter: "RCS: A System for Version Control", page 15. Department of Computer Science Technical Reports, Purdue University. Paper 394. https://docs.lib.purdue.edu/cstech/394
- ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
Notes
- Walter F. Tichy: RCS--A System for Version Control. In: Software: Practice and Experience. July 1985. Volume 15. Number 7. Pages 637–654. References to the paper at CiteSeer alternate link to paper
Further reading
[edit | edit source]- Don Bolinger, Tan Bronson, Applying RCS and SCCS - From Source Control to Project Control. O'Reilly, 1995.
- Walter F. Tichy, RCS—A System for Version Control Archived 18 February 2018 at the Wayback Machine, 1985
- Paul Heinlein, RCS HOWTO, 2004
External links
[edit | edit source]Lua error in mw.title.lua at line 392: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal').
- Original RCS at Purdue
- : RCS file management program – OpenBSD General Commands Manual
Lua error in Module:Authority_control at line 153: attempt to index field 'wikibase' (a nil value).