Source Code Control System

Last updated
Source Code Control System (SCCS)
Original author(s) Marc J. Rochkind
Developer(s) Bell Labs
Initial release1973;50 years ago (1973)[ discuss ]
Repository N/A
Written inFirst version: SNOBOL4
Rewrite: C
Operating system OS/360, Unix, Unix-like
Platform IBM System/370, PDP-11, IA-32
Type Version control
License proprietary licenses, Common Development and Distribution License
Website The Open Group Base Specifications Issue 7, IEEE Std 1003.1-2008, 2016 Edition

Source Code Control System (SCCS) is a version control system designed to track changes in source code and other text files during the development of a piece of software. This allows the user to retrieve any of the previous versions of the original source code and the changes which are stored. It was originally developed at Bell Labs beginning in late 1972 by Marc Rochkind for an IBM System/370 computer running OS/360. [1]

Contents

A characteristic feature of SCCS is the sccsid string that is embedded into source code, and automatically updated by SCCS for each revision. [2] This example illustrates its use in the C programming language:

 static char sccsid[] = "@(#)ls.c        8.1 (Berkeley) 6/11/93";

This string contains the file name, date, and can also contain a comment. After compilation, the string can be found in binary and object files by looking for the pattern @(#) and can be used to determine which source code files were used during compilation. The what command is available to automate this search for version strings. [3]

History

In 1972, Marc Rochkind developed SCCS in SNOBOL4 at Bell Labs for an IBM System/370 computer running OS/360 MVT. [1] He rewrote SCCS in the C programming language for use under UNIX, then running on a PDP-11, in 1973.

The first publicly released version was SCCS version 4 from February 18, 1977. [4] It was available with the Programmer's Workbench (PWB) edition of the operating system. Release 4 of SCCS was the first version that used a text-based history file format, earlier versions did use binary history file formats. Release 4 was no longer written or maintained by Marc Rochkind. Subsequently, SCCS was included in AT&T's commercial System III and System V distributions. It was not licensed with 32V, the ancestor to BSD. [5] The SCCS command set is now part of the Single UNIX Specification.

SCCS was the dominant version control system for Unix until later version control systems, notably the RCS and later CVS, gained more widespread adoption. Today, these early version control systems are generally considered obsolete, particularly in the open-source community, which has largely embraced distributed version control systems. However, the SCCS file format is still used internally by a few newer version control programs, including BitKeeper and TeamWare . The latter is a frontend to SCCS. Sablime Archived 2016-07-22 at the Wayback Machine has been developed from a modified version of SCCS [6] but uses a history file format that is incompatible with SCCS. The SCCS file format uses a storage technique called interleaved deltas (or the weave [7] ). This storage technique is now considered by many version control system developers as foundational to advanced merging and versioning techniques, [8] such as the "Precise Codeville" ("pcdv") merge.

Apart from correcting Year 2000 problems in 1999, no active development has taken place on the various UNIX vendor-specific SCCS versions. [9] In 2006, Sun Microsystems (today part of Oracle) released their Solaris version of SCCS as open-source under the CDDL license as part of their efforts to open-source Solaris. [10]

Background

The Source Code Control System (SCCS) is a system for controlling file and history changes. Software is typically upgraded to a new version by fixing bugs, optimizing algorithms and adding extra functions. [11] Changing software causes problems that require version control to solve. [1]

SCCS was built to solve these problems. SCCS from AT&T had five major versions for the IBM OS and five major versions for UNIX [12] Two specific implementations using SCCS are: PDP 11 under Unix and IBM 370 under the OS. [1]

Composition

SCCS consists of two parts: SCCS commands and SCCS files. [13] All basic operations (e.g., create, delete, edit) can be realized by SCCS commands. [13] SCCS files have a unique format prefix s., which is controlled by SCCS commands. [2]

SCCS files

An SCCS file consists of three parts: [14]

Delta table

In SCCS, a delta is a single revision in an SCCS file. Deltas are stored in a delta table, so each SCCS file has its own record of changes. [14]

Control and tracking flags in SCCS files

Every operation of each SCCS file is tracked by flags. Their functions are as below: [14]

Body

SCCS uses three types of control records for keeping track of insertions and deletions applied in different deltas. They are the insertion control record, the deletion control record, and the end control record. Whenever a user changes some part of the text, a control record is inserted surrounding the change. The control records are stored in the body along with the original text records. [1]

SCCS basic commands

SCCS provides a set of commands in the form of macro invocations that perform or initiate source code management functions with a simple syntax, such as create, get, edit, prt. [15] [16] It also provides access to the revision history of files under management. These commands are implemented as argument verbs to the driver program sccs.

Create

The sccs command create uses the text of a source file to create a new history file. For example:

$ sccscreateprogram.c program.c:1.187 lines

The outputs are name, version and lines.

The command is a macro that expands to admin to create the new history file followed by get to retrieve the file.

Edit

$ sccseditprogram.c 1.1new delta 1.287 lines

Edit a specific file.

The command is a macro that expands to get -e.

Delget

$ sccsdelgetprogram.c comments? main function enhanced1.210 inserted0 deleted87 unchanged1.297 lines

Check in new version and get the new version from sccs.

The command is a macro that expands to delta to check in the new version file followed by get to retrieve the file.

Get

$ sccsgetprogram.c 1.187 lines

The outputs are version and lines you want to get from specific file.

Prt

$ sccsprtprogram.c

This command produces a report of source code changes.

Implementations

UNIX SCCS versions

Most UNIX versions include a version of SCCS, which, however, is often no longer actively developed. [17] [ better source needed ]

Jörg Schilling's fork

The late Jörg Schilling  [ de ] (who requested the release of SCCS in the early days of the OpenSolaris project) [18] maintained a fork of SCCS [19] [20] that is based on the OpenSolaris source code. It has received major feature enhancements but remains compatible with the original SCCS versions unless using the "new project" mode. [21]

Heirloom Project

The Heirloom Project includes a version of SCCS derived from the OpenSolaris source code [22] and maintained between December 2006 and April 2007. [23]

GNU conversion utility

GNU offers the SCCS compatible program GNU CSSC ("Compatibly Stupid Source Control"), which is occasionally used to convert SCCS archives to newer systems like CVS or Subversion; [24] it is not a complete [25] SCCS implementation and not recommended for use in new projects, but mostly meant for converting to a modern version control system.

Other version control systems

Since the 1990s, many new version control systems have been developed and become popular that are designed for managing projects with a large number of files and that offer advanced functionality such as multi-user operation, access control, automatic building, network support, release management and distributed version control. Bitkeeper and TeamWare use the SCCS file format internally and can be considered successors to SCCS. [26] [27]

On BSD systems, the SCCSID is replaced by a RCSID starting and ending with $; the corresponding tool is ident. [28] This system is originally used by RCS and added automatically on checkout. The resulting source code revision control identifiers are documented in the NetBSD [29] and FreeBSD [30] style guides for their own code bases. NetBSD defines the custom keyword $NetBSD: ...$ while FreeBSD defines $FreeBSD: ...$ and a macro renamed __FBSDID.

The SRC version control system can also use the SCCS file format internally (or RCS's) and aims to provide a better user interface for SCCS while still managing only single-file projects. [31]

Related Research Articles

The Single UNIX Specification (SUS) is a standard for computer operating systems, compliance with which is required to qualify for using the "UNIX" trademark. The standard specifies programming interfaces for the C language, a command-line shell, and user commands. The core specifications of the SUS known as Base Specifications are developed and maintained by the Austin Group, which is a joint working group of IEEE, ISO/IEC JTC 1/SC 22/WG 15 and The Open Group. If an operating system is submitted to The Open Group for certification, and passes conformance tests, then it is deemed to be compliant with a UNIX standard such as UNIX 98 or UNIX 03.

troff, short for "typesetter roff", is the major component of a document processing system developed by Bell Labs for the Unix operating system. troff and the related nroff were both developed from the original roff.

In computing, a core dump, memory dump, crash dump, storage dump, system dump, or ABEND dump consists of the recorded state of the working memory of a computer program at a specific time, generally when the program has crashed or otherwise terminated abnormally. In practice, other key pieces of program state are usually dumped at the same time, including the processor registers, which may include the program counter and stack pointer, memory management information, and other processor and operating system flags and information. A snapshot dump is a memory dump requested by the computer operator or by the running program, after which the program is able to continue. Core dumps are often used to assist in diagnosing and debugging errors in computer programs.

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.

man page Unix software documentation

A man page is a form of software documentation usually found on a Unix or Unix-like operating system. Topics covered include computer programs, formal standards and conventions, and even abstract concepts. A user may invoke a man page by issuing the man command.

In computing, tar is a computer software utility for collecting many files into one archive file, often referred to as a tarball, for distribution or backup purposes. The name is derived from "tape archive", as it was originally developed to write data to sequential I/O devices with no file system of their own. The archive data sets created by tar contain various file system parameters, such as name, timestamps, ownership, file-access permissions, and directory organization. POSIX abandoned tar in favor of pax, yet tar sees continued widespread use.

ls Command to list files and directories in Unix and Unix-like operating systems

In computing, ls is a command to list computer files and directories in Unix and Unix-like operating systems. It is specified by POSIX and the Single UNIX Specification.

In software development, Make is a build automation tool that builds executable programs and libraries from source code by reading files called makefiles which specify how to derive the target program. Though integrated development environments and language-specific compiler features can also be used to manage a build process, Make remains widely used, especially in Unix and Unix-like operating systems.

compress is a Unix shell compression program based on the LZW compression algorithm. Compared to gzip's fastest setting, compress is slightly slower at compression, slightly faster at decompression, and has a significantly lower compression ratio. 1.8 MiB of memory is used to compress the Hutter Prize data, slightly more than gzip's slowest setting.

<span class="mw-page-title-main">History of software configuration management</span>

The history of software configuration management (SCM) in computing can be traced back as early as the 1950s, when CM, originally for hardware development and production control, was being applied to software development. The first software configuration management was most likely done manually. Eventually, software tools were written to manage software changes. History records tend to be based on tools and companies, and lend concepts to a secondary plane.

patch (Unix) Unix utility to apply changes to text files

The computer tool patch is a Unix program that updates text files according to instructions contained in a separate file, called a patch file. The patch file is a text file that consists of a list of differences and is produced by running the related diff program with the original and updated file as arguments. Updating files with patch is often referred to as applying the patch or simply patching the files.

pax is an archiving utility available for various operating systems and defined since 1995. Rather than sort out the incompatible options that have crept up between tar and cpio, along with their implementations across various versions of Unix, the IEEE designed new archive utility pax that could support various archive formats with useful options from both archivers. The pax command is available on Unix and Unix-like operating systems and on IBM i, and Microsoft Windows NT until Windows 2000.

In computing, a dynamic linker is the part of an operating system that loads and links the shared libraries needed by an executable when it is executed, by copying the content of libraries from persistent storage to RAM, filling jump tables and relocating pointers. The specific operating system and executable format determine how the dynamic linker functions and how it is implemented.

In Unix computing, crypt or enigma is a utility program used for encryption. Due to the ease of breaking it, it is considered to be obsolete.

In software development, version control is a class of systems responsible for managing changes to computer programs or other collections of information such that revisions have a logical and consistent organization. The following tables include general and technical information on notable version control and software configuration management (SCM) software. For SCM software not suitable for source code, see Comparison of open-source configuration management software.

sum is a legacy utility available on some Unix and Unix-like operating systems. This utility outputs a 16-bit checksum of each argument file, as well as the number of blocks they take on disk. Two different checksum algorithms are in use. POSIX abandoned sum in favor of cksum.

chattr is the command in Linux that allows a user to set certain attributes of a file. lsattr is the command that displays the attributes of a file.

<span class="mw-page-title-main">Unix</span> Family of computer operating systems

Unix is a family of multitasking, multi-user computer operating systems that derive from the original AT&T Unix, whose development started in 1969 at the Bell Labs research center by Ken Thompson, Dennis Ritchie, and others.

References

  1. 1 2 3 4 5 Rochkind, Marc J. (December 1975), "The Source Code Control System" (PDF), IEEE Transactions on Software Engineering, vol. SE-1, no. 4, pp. 364–370, doi:10.1109/tse.1975.6312866, S2CID   10006076, archived from the original (PDF) on 2011-05-25, retrieved 2005-07-08
  2. 1 2 Oracle. "Chapter 5 SCCS Source Code Control System". Programming Utilities Guide.
  3. ↑ "what". IEEE and The Open Group. n.d. Retrieved November 28, 2022.
  4. ↑ http://sccs.sourceforge.net/PWB.html AT&T Announcement for SCCSv4
  5. ↑ SCCS what(1) manpage from 4BSD, 1980, on the website of The Unix Heritage Society Archived 2005-08-31 at the Wayback Machine .
  6. ↑ Estublier, Jacky, David Leblang, André van der Hoek, Reidar Conradi, Geoffrey Clemm, Walter Tichy, and Darcy Wiborg-Weber. “Impact of software engineering research on the practice of software configuration management.” ACM Transactions on Software Engineering and Methodology (TOSEM) 14 (October 2005): 383–430.
  7. ↑ Hudson, Greg (2002-10-03), Notes on keeping version histories of files, Unpublished personal notes
  8. ↑ Estublier, Jacky, David Leblang, André van der Hoek, Reidar Conradi, Geoffrey Clemm, Walter Tichy, and Darcy Wiborg-Weber. “Impact of software engineering research on the practice of software configuration management.” ACM Transactions on Software Engineering and Methodology (TOSEM) 14 (October 2005): p.398.
  9. ↑ What is SCCS, GNU operating System
  10. ↑ Stephen Lau, Sun Microsystems (2006-12-19). "SCCS/make source available". Archived from the original on April 25, 2012. Retrieved 2011-11-14.
  11. ↑ Home Organization Selection ProQuest   215925387
  12. ↑ The evolution of a Source Code Control System. Alan L.Glasser, published in sigmetrics, Nov 1978 when SCCS on UNIX was a version 4
  13. 1 2 "SCCS". www-h.eng.cam.ac.uk. Retrieved 2016-09-12.
  14. 1 2 3 IBM (7 June 2018). "General Programming Concepts: Writing and Debugging Programs". IBM Knowledge Center.
  15. ↑ An Introduction to the Source Code Control System Eric Allman, Project Ingres, University of California at Berkeley
  16. ↑ Source Code Control System Programming Utilities Guide
  17. ↑ Koike, Hideki, and Hui-Chu Chu. "VRCS: Integrating version control and module management using interactive three-dimensional graphics." Visual Languages, 1997. Proceedings. 1997 IEEE Symposium on. IEEE, 1997.
  18. ↑ "os.solaris.opensolaris.rfe - Re: star - msg#00001 - Recent Discussion OSDir.com". osdir.com. Retrieved 10 September 2016.
  19. ↑ Jörg Schilling's SCCS development website
  20. ↑ "A collection of tools written or formerly managed by Jörg Schilling". Codeberg . 22 October 2022. Retrieved 28 November 2022. development has been picked up by a group of volunteers who would like to keep the project alive and well
  21. ↑ Schily SCCS web site: "Will the upcoming SCCSv6 stay compatible with POSIX and with historic SCCS implementations?"
  22. ↑ Gunnar Ritter (20 June 2010). "The Heirloom Development Tools" . Retrieved 4 November 2011.
  23. ↑ http://heirloom.cvs.sourceforge.net/viewvc/heirloom/heirloom-devtools/sccs/ see CVS history
  24. ↑ SCCS2SVN conversion utility Archived 2009-12-22 at the Wayback Machine , which works with both SCCS and CSSC
  25. ↑ GNU CSSC list of limitations in its documentation
  26. ↑ "revtool". BitKeeper Documentation.
  27. ↑ "Introduction to Sun WorkShop TeamWare". docs.oracle.com. Retrieved 10 September 2016.
  28. ↑ ident(1)  –  NetBSD General Commands Manual
  29. ↑ "src/share/misc/style revision 1.64". NetBSD CVS repository.
  30. ↑ style(9)  –  FreeBSD Kernel Developer's Manual
  31. ↑ "Resource page for src 1.29". January 21, 2022. Retrieved November 28, 2022.

Further reading

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.