naked SCCS really SCCS!

[Tim Oldham]

In article <1580 at auspex.auspex.com> guy at auspex.auspex.com (Guy Harris) writes:
>>Bullshit.  It has done a damn good job for me, and front-end interfaces just
>>add more steps without adding appreciable functionality or ease of use.
>
>Bullshit.  I find "admin" a pain to use; the BSD "sccs" front-end
>program's "sccs create" and "sccs enter" programs make it much nicer -
>it takes *fewer* steps to use them than to use full-frontal "admin". 

Hear hear. But the trouble with sysV sccs is the brain-damaged way it
keeps all the s- and p-files in the directory you're working in. Crazy!
Apart from anything else (directory clutter, making it harder to write
shell scripts 'cos matching *.c doesn't work any more, etc.), SCCS
ought to be transparent. And what's happened to fix? Wow, so I can cdc
to change the delta commentary, but that's not a great deal of help.
I always feel guilty using chmod, vi and admin -z around s-files,
and quite right too.

If anyone can tell me how to get sccs to use an SCCS directory, I'd
be *extremely* grateful. Anyone have a fix program for sysV they can
distribute?

	Tim.
-- 
Tim Oldham      ...!mcvax!ukc!axion!fulcrum!tjo  or  tjo at fulcrum.bt.co.uk
#include	<stdisclaim>
Why have coffee, when caffeine tastes this good?