Source Code Control System

Source Code Control System
Original author(s) Marc J. Rochkind
Initial release 1972 (1972)
Written in C
Operating system Unix-like
Type Version control
License proprietary licenses, Common Development and Distribution License

Source Code Control System (SCCS) is an early version control system, geared toward program source code and other text files. It was originally developed in SNOBOL at Bell Labs in 1972 by Marc Rochkind for an IBM System/370 computer running OS/360 MVT.[1] It was later rewritten by him in C for UNIX, then running on a PDP-11, and released with the Programmer's Workbench (PWB) edition of that operating system.

Subsequently, SCCS was included in AT&T's commercial System III and System V distributions. It was not licensed with 32V, the ancestor to Berkeley Unix.[2] 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 Revision Control System (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 has been developed from a modified version of SCCS[3] 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[4]). This storage technique is now considered by many version control system developers as foundational to advanced merging and versioning techniques,[5] such as the "Precise Codeville" ("pcdv") merge.

Apart from fixing some Year 2000 problems in 1999, there is no active development on the various UNIX vendor specific SCCS versions.[6] In 2006, Sun Microsystems (today part of Oracle Corporation) released their Solaris version of SCCS as open source under the Common Development and Distribution License as part of their efforts to open-source Solaris.[7]

SCCS is also known for the sccsid string, for example:

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.

Background

The Source Code Control System (SCCS) is a system for controlling file and history changes. Source upgrade is one of the most significant parts in modern software development. In general, software upgraded to be a new version by fixing bugs, optimizing algorithms and adding extra functions.[8] Obviously, many famous software have lots of versions，such as Java.[9] However, additional problems occurs associate with these changes.[10]

Therefore, Source Code Control System, the most powerful weapon to solve these problems, appeared in developers' world. SCCS itself had a lot of changes during the past time.The SCCS has nine different major versions which are designed to help programmers control changes as a software. The differences are about facilities and design changes in terms of problem solving.[11] Two specific successful implementations using SCCS : PDP 11 under Unix and IBM 370 under the OS.[12]

Composition

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

SCCS Files

An SCCS file is composed by three different parts:[15]

Delta table

In SCCS, a delta refers to a change of SCCS file. Deltas are stored in a delta table, so each SCCS file has its own record of changes.[15]

Control and Tracking Flags in SCCS Files

Every operation of each SCCS file will be tracked by flags. Their functions are as below:[15]

SCCS Basic Commands

There are lots of commands that can be used in SCCS. These commands help us to finish what we want to achieve without understanding how they worked.[16] Also, the SCCS allows us to have access to history files. Moreover, it also provides some commands which allow us to edit, monitor and change the source files.[17]

Create

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

$ sccs create program.c

program.c:

1.1

87 lines

The outputs are name, version and lines.

Edit

$ sccs edit program.c

1.1

new delta 1.2

87 lines

Edit a specific file.

Get

sccs get program.c

1.1

87 lines

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

Prt

sccs prt program.c

This command produces a report of changes you made.

Alternatives

UNIX SCCS versions

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

Jörg Schilling's fork

Jörg Schilling (who requested the release of SCCS in the early days of the OpenSolaris project)[19] maintains a fork of SCCS[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]

References

  1. ↑ Rochkind, Marc J. (December 1975), "The Source Code Control System" (PDF), IEEE Transactions on Software Engineering, SE–1 (4), pp. 364–370
  2. ↑ SCCS what(1) manpage from 4BSD, 1980, on the website of The Unix Heritage Society.
  3. ↑ 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.
  4. ↑ Hudson, Greg (2002-10-03), Notes on keeping version histories of files, Unpublished personal notes
  5. ↑ 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.
  6. ↑ What is SCCS, GNU operating System
  7. ↑ Stephen Lau, Sun Microsystems (2006-12-19). "SCCS/make source available". Archived from the original on April 25, 2012. Retrieved 2011-11-14.
  8. ↑ "Home Organization Selection". search.proquest.com.prox.lib.ncsu.edu. Retrieved 2016-09-12.
  9. ↑ "Java Downloads for All Operating Systems". java.com. Retrieved 2016-09-11.
  10. ↑ J.Rochkind, Marc. "IEEE Xplore Document - The source code control system". ieeexplore.ieee.org.
  11. ↑ The evolution of a Source Code Control System. Alan L.Glasser, published in sigmetrics,Nov 1978
  12. ↑ The Source Code Control System Rochkind, Marc J. "The source code control system." IEEE Transactions on Software Engineering 4 (1975): 364-370
  13. 1 2 "SCCS". www-h.eng.cam.ac.uk. Retrieved 2016-09-12.
  14. ↑ Oracle. "Chapter 5 SCCS Source Code Control System". Programming Utilities Guide.
  15. 1 2 3 IBM. "General Programming Concepts: Writing and Debugging Programs". IBM Knowledge Center.
  16. ↑ An Introduction to the Source Code Control System Eric Allman, Project Ingres, University of California at Berkeley
  17. ↑ Source Code Control System Programming Utilities Guide
  18. ↑ 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.
  19. ↑ "os.solaris.opensolaris.rfe - Re: star - msg#00001 - Recent Discussion OSDir.com". osdir.com. Retrieved 10 September 2016.
  20. ↑ Jörg Schilling's SCCS development website
  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, which works with both SCCS and CSSC
  25. ↑ GNU CSSC list of limitations in its documentation
  26. ↑ "revtool | BitKeeper Documentation". www.bitkeeper.org.
  27. ↑ "Introduction to Sun WorkShop TeamWare". docs.oracle.com. Retrieved 10 September 2016.
This article is issued from Wikipedia - version of the 11/28/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.