Path: utzoo!attcan!uunet!husc6!spdcc!esegue!johnl
From: johnl@iecc.cambridge.ma.us (John R. Levine)
Newsgroups: comp.unix.programmer
Subject: Re: SCCS REVISION HISTORY
Keywords: SCCS revision history source
Message-ID: <1990Oct29.053733.20959@iecc.cambridge.ma.us>
Date: 29 Oct 90 05:37:33 GMT
References: <143950@sun.Eng.Sun.COM> <1990Oct25.163501.16809@eci386.uucp> <1762@b15.INGR.COM> <1990Oct28.190212.21838@eci386.uucp>
Reply-To: johnl@iecc.cambridge.ma.us (John R. Levine)
Organization: I.E.C.C., Cambridge MA 02238
Lines: 21

In article <1990Oct28.190212.21838@eci386.uucp> woods@eci386.UUCP (Greg A. Woods) writes:
>Sccs is covered by the Berkeley Software Distribution copyright, and
>is essentially freeware.

That's hard to believe.  SCCS was written at Bell Labs for PWB.  Every
version I've ever seen looks to be largely unchanged from the original code.
Perhaps you're thinking of RCS which is now under the Gnu copyleft.

As far as SCCS front ends go, I've been quite satisfied with some smallish
(on the order of 100 lines) shell scripts which I've written many times that
let you maintain parallel local source and global sccs trees.  For example,
if you are in your directory foo/bar and say "Get filexx" it turns into a
get of /usr/sccs/foo/bar/s.filexx.  A little more shell hackery keeps in each
directory a list of checked out files in that directory, for use in "Put"
scripts to check them all back in at once, and in makefiles to force
recompilation of all the checked out sources.

-- 
John R. Levine, IECC, POB 349, Cambridge MA 02238, +1 617 864 9650
johnl@iecc.cambridge.ma.us, {ima|spdcc|world}!esegue!johnl
"Although the moon is smaller than the earth, it is also farther away."