Revision Control System
|Original author(s)||Walter F. Tichy|
|Stable release||5.9.4 (January 22, 2015) [±]|
|License||GNU General Public License|
The Revision Control System (RCS) is a software implementation of revision control that automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, for example programs, documentation, procedural graphics, papers, and form letters. RCS is also capable of handling binary files, though with reduced efficiency. Revisions are stored with the aid of the diff utility.
RCS was first released in 1982  by Walter F. Tichy while he was at Purdue University. RCS was an alternative to the then-popular Source Code Control System (SCCS). It is currently maintained by the GNU Project.
Initially (through version 3, which was distributed in 4.3BSD), its license prohibited redistribution without written permission from Walter Tichy:
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.
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.
Mode of operation
RCS operates only on single files; it has no way of working with an entire project, so it does not support atomic commits affecting multiple files. Although it provides branching for individual files, the version syntax is cumbersome. Instead of using branches, many teams just use the built-in locking mechanism and work on a single head branch.
Concurrent Versions System (CVS)
A simple system called CVS was developed, capable of dealing with RCS files en masse, and this was the next natural step of evolution of this concept, as it “transcends but includes” elements of its predecessor. CVS was originally a set of scripts which used RCS programs to manage the files. It no longer does that; rather, it operates directly on the files.
Project Revision Control System (PRCS)
In single-user scenarios, such as server configuration files or automation scripts, RCS may still be the preferred revision control tool as it is simple and no central repository needs to be accessible for it to save revisions. This makes it a more reliable tool when the system is in dire maintenance conditions. Additionally, the saved backup files are easily visible to the administration so the operation is straightforward. However, there are no built-in tamper protection mechanisms (that is, users who can use the RCS tools to version a file also, by design, are able to directly manipulate the corresponding version control file) and this is leading some security conscious administrators to consider client/server version control systems that restrict users' ability to alter the version control files.
- "GNU RCS". directory.fsf.org. FSF. 22 January 2015.
- "RCS man page". Retrieved 2010-02-07.
- Tichy, Walter (1982). "Design, implementation, and evaluation of a Revision Control System". ICSE '82 Proceedings of the 6th international conference on Software engineering: 58–67. Retrieved 12 June 2012.
- "RCS". GNU Project. Free Software Foundation. 22 Jan 2015. Retrieved 27 June 2015.
- "4.3BSD - /usr/src/new/rcs/src/rcsdiff.c". Walter's Retro Computing Corner Documentation. May 19, 1986. Retrieved November 15, 2014.
- "CSRG/cd2/4.3reno/usr/src/contrib/rcs/src/READ_ME". February 27, 1989.
- "CSRG/cd2/4.3reno/usr/src/contrib/rcs/src/rcs.c". August 15, 1989.
- RCS 4.3 README file.
- MacDonald, Joshua P (May 9, 2004). "PRCS, the Project Revision Control System". Retrieved 2008-12-12.
- Don Bolinger, Tan Bronson, Applying RCS and SCCS - From Source Control to Project Control. O'Reilly, 1995.