Software Configuration Management, commonly taken to mean "source code management", which is more general than "version control", but is often viewed merely in terms of the latter.
- A tiny version control
- Very minimal, but helpful on small devices.
- choice of SCM for the Tcl/Tk core
- tools for determining the difference between to texts.
- Comparison of revision control software , Wikipedia
- More comprehensive than the content below.
- The Tcl FAQ, part 4
- a huge but old list of other programs, including SCM systems and interfaces
In "enterprise"- or management-dominated IT circles, it'll be understood as "supply chain management", which is regarded as automatable commercially.
- Separate commits for separate issues is very helpful, folks.
- - dgp, Tcl Chatroom, 2015-04-03
- Source Control HOWTO , Eric Sink
- Software Configuration Management FAQ for comp.software.config-mgmt
- Obsolete. Retained online only for archival purposes.
Tcl Integrated SCM Systems
- Fossil, by DRH
- Qualifies as a Tcl tool because of its close integration with Tcl. Popular in the Tcl community.
Non-Tcl Integrated SCM Systems
- More mature, hosted, originally provided only CVS repositories.
Tcl Revision Control Tools
- Transaction-based. Open-Source. Sports a Tk interface.
- At least initially written in Tcl/Tk.
- BitKeeper, originally by Larry McVoy
- Decentralized, Proprietary. Uses Tcl extensively.
- A SCM tool written in tcl/tk and act as subversion and CVS client. It uses tkdiff.
- Written in Tcl, built on top of RCS.
Non-Tcl Revision Control Tools
- Distributed, open-source, written in Python.
- A reporting tool for CVS.
- Centralized, old skool.
- Centralized. Developed as an alternative to CVS.
- git, by Linux Torvalds
- Distributed, written in C.
- distributed, open-source, written in Python
- Predates CVS.
- In the beginning, there was SCCS.
- Serena Dimensions
- Centralized. Proprietary.
- Mentioned occasionally as useful in interacting with these SCM environments.
Tcl Issue Tracking Tools
- Uses SQLite, and oddly enough, its source code is hosted in Fossil.
Non-Tcl Issue Tracking Tools
- open-source, long history, widely-used. Bugzilla 1.0 was written in Tcl, with later versions written in Perl.
The two expansions of the acronym SCM mean different things to SCM specialists - see
news:comp.software.config-mgmt and its FAQ [1 ].
A variety of Software Configuration Management/Source Code Management strategies are available.
SCM tools with Tcl connections
There had been a few other tools with connection to tcl/tk, that has faded as much as not having a homepage on the Internet. They are:
| What:|| boob|
| Where:|| From the contact|
| Description:|| Tool Object oriented objection builder which manages SCM builds and repository duties. Written in itcl and uses itcl files as dependencies and build scripts. Rules based dependencies with on the fly scanning of c/c++ files.|
| Updated:|| 10/1998|
| Contact:|| mailto:[email protected] (Bob McWhirter)|