kriz@rdp1.UUCP (patti krizowsky) (03/21/91)
On March 14, I posted a request for information and opinions on an
SCCS front end. I'd like to thank everyone for taking the time to
reply to my post. In summary, most people recommended RCS (Revision
Control System) as an alternative to SCCS, and recommended CVS
(Concurrent Versions System) as a front-end to RCS. RCS and CVS
can be found on the following sites, and probably on many others:
archive.cs.ruu.nl /pub/GNU/rcs-5.5.tar.Z
cs.purdue.edu put/RCS/rcs.5.5.tar.Z
prep.ai.mit.edu pub/gnu/rcs-5.5.tar.Z
uunet.uu.net gnu/rcs-5.5.tar.Z
I have compiled RCS and CVS on our system (Unisys 6000/55, SysV R3.2)
and we are testing it out.
Also recommended was Berkeley's SCCS front-end, available from
uunet.uu.net in bsd-source/usr.bin/sccs. I have yet to retrieve
it, but I plan on getting it and testing it out soon.
I also was given some things to consider about what would be involved
in writing our own front end, such as documentation, training,
support, etc.
I'd like to thank the following people for taking the time to reply
to my posting. They have given me valuable ideas and alternatives
to consider.
---
Thanks to Tom Christiansen (tchrist@convex.COM), who posted a reply
that sent me off to retrieve and review RCS and CVS.
---
Thanks to Andrew Marrinson (icom!xwkg.icom.com!andy) for recommending
Berkeley's SCCS front-end.
---
Thanks to Paul Eggert (CS.UCLA.EDU!twinsun!twinsun.com!eggert) for
recommending RCS/CVS and Berkeley's front-end.
---
Thanks to Lou Kates (watmath!tslwat!louk) for e-mailing me a
comparison of SCCS and RCS.
---
Thanks to Allan Doyle (BBN.COM!vax.bbn.com!bbn.com!adoyle) for
giving me some things to consider before attempting to write our
own front end.
---
Thanks again, everyone!
patti
--
patti krizowsky e-mail: rdp1!kriz
federal paper board
"Why waste time learning, when ignorance is instantaneous?"
- Hobbes, of Calvin &