Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!hplabs!sri-unix!gwyn@BRL-VLD.ARPA From: gwyn@BRL-VLD.ARPA Newsgroups: net.unix-wizards Subject: Re: SCCS and RCS Message-ID: <1468@sri-arpa.UUCP> Date: Fri, 29-Jun-84 20:59:59 EDT Article-I.D.: sri-arpa.1468 Posted: Fri Jun 29 20:59:59 1984 Date-Received: Sat, 14-Jul-84 13:27:51 EDT Lines: 18 From: Doug Gwyn (VLD/VMB) Funny that you should know that SCCS is of Berkeley origin. I rather thought Mashey & crew had developed it as part of the PWB project at Bell Labs. SCCS is now a standard part of UNIX System III and V, and is described in the documentation accompanying those systems. RCS started as a "public domain" equivalent (by Walter Tichy of Purdue) and is distributed with 4.2BSD. We use both at BRL and they each have strong and weak points. One of the nicest things about SCCS these days is the support for it in the "make" utility. Many of our application codes are maintained as a collection of SCCS archives; typing "make install clobber" in the appropriate directory extracts the makefile and all the required sources from the archives, and cleans up after the product has been tested and installed. Automation is great. A complete software project management system would need much more than just a source document revision control system. There have been many such more complete systems discussed at USENIX conferences (MASCOT comes to mind, and Mashey discussed such a system a couple years ago).