Editing Source Code Control System (section)

==Implementations==

=== UNIX SCCS versions ===
Most [[UNIX]] versions include a version of SCCS, which, however, is often no longer actively developed.<ref>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.</ref>{{better source needed|date=September 2016}}

=== Jörg Schilling's fork ===
The late {{ill|Jörg Schilling|de}} (who requested the release of SCCS in the early days of the [[OpenSolaris]] project)<ref>{{cite web|title=os.solaris.opensolaris.rfe - Re: star - msg#00001 - Recent Discussion OSDir.com|url=http://osdir.com/ml/os.solaris.opensolaris.rfe/2006-05/msg00001.html|website=osdir.com|access-date=10 September 2016}}</ref> maintained a [[Fork (software development)|fork]] of SCCS<ref name="schily-sccs">[http://sccs.sourceforge.net/ Jörg Schilling's SCCS development website]</ref><ref>{{cite web |url=https://codeberg.org/schilytools/schilytools/src/branch/master/AN-2022-10-16 |title=A collection of tools written or formerly managed by Jörg Schilling. |author=<!--Not stated--> |date=22 October 2022 |website=[[Codeberg]] |access-date=28 November 2022 |quote=development has been picked up by a group of volunteers who would like to keep the project alive and well}}</ref> 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.<ref>[http://sccs.sourceforge.net/#compatibility Schily SCCS web site]: "Will the upcoming SCCSv6 stay compatible with POSIX and with historic SCCS implementations?"</ref>

=== Heirloom Project ===
The [[Heirloom Project]] includes a version of SCCS derived from the [[OpenSolaris]] source code<ref>{{cite web |url=http://heirloom.sourceforge.net/devtools.html |title=The Heirloom Development Tools |author=Gunnar Ritter |date=20 June 2010 |access-date=4 November 2011}}</ref> and maintained between December 2006 and April 2007.<ref>http://heirloom.cvs.sourceforge.net/viewvc/heirloom/heirloom-devtools/sccs/ see CVS history</ref>

=== GNU conversion utility ===
[[GNU]] offers the SCCS compatible program [https://www.gnu.org/software/cssc/ GNU CSSC] ("Compatibly Stupid Source Control"), which is occasionally used to convert SCCS archives to newer systems like [[Concurrent Versions System|CVS]] or [[Subversion (software)|Subversion]];<ref>[http://sccs2svn.berlios.de/ SCCS2SVN conversion utility] {{webarchive|url=https://web.archive.org/web/20091222091016/http://sccs2svn.berlios.de/ |date=2009-12-22 }}, which works with both SCCS and CSSC</ref> it is not a complete<ref>[https://www.gnu.org/s/cssc/manual/Incomplete.html#Incomplete GNU CSSC list of limitations in its documentation]</ref> 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, [[List of version control software|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.<ref>{{cite web|title=revtool|work=BitKeeper Documentation|url=https://www.bitkeeper.org/man/revtool.html}}</ref><ref>{{cite web|title=Introduction to Sun WorkShop TeamWare|url=https://docs.oracle.com/cd/E19957-01/806-3573/intro.html|website=docs.oracle.com|access-date=10 September 2016}}</ref>

On BSD systems, the SCCSID is replaced by a RCSID starting and ending with {{mono|$}}; the corresponding tool is {{mono|ident}}.<ref>{{Man|1|ident|NetBSD}}</ref> This system is originally used by [[Revision Control System|RCS]] and added automatically on checkout. The resulting source code revision control identifiers are documented in the [[NetBSD]]<ref>{{cite web|title=src/share/misc/style revision 1.64|url=http://cvsweb.netbsd.org/bsdweb.cgi/src/share/misc/style?rev=1.64&content-type=text/x-cvsweb-markup|publisher=NetBSD CVS repository}}</ref> and [[FreeBSD]]<ref>{{Man|9|style|FreeBSD}}</ref> style guides for their own code bases. NetBSD defines the custom keyword {{mono|$NetBSD: ...$}} while FreeBSD defines {{mono|$FreeBSD: ...$}} and a macro renamed {{mono|__FBSDID}}.

The SRC version control system can also use the SCCS file format internally (or [[Revision Control System|RCS]]'s) and aims to provide a better user interface for SCCS while still managing only single-file projects.<ref>{{cite web |url=http://www.catb.org/esr/src/ |title=Resource page for src 1.29 |author=<!--Not stated--> |date=January 21, 2022 |access-date=November 28, 2022 |quote=}}</ref>