Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!bpa!cbmvax!vu-vlsi!mpx1!mpx2!erik
From: erik@mpx2.mpx.com (Erik Murrey)
Newsgroups: comp.unix.questions
Subject: Re: SCCS vs RCS
Message-ID: <10006@mpx2.mpx.com>
Date: 8 Jun 89 15:08:12 GMT
References: <19885@adm.BRL.MIL> <2934@mentor.cc.purdue.edu>
Reply-To: erik@mpx2.mpx.com (Erik Murrey)
Organization: MPX Data Systems, Inc. ,  Wayne, PA
Lines: 24

In article <19885@adm.BRL.MIL> mark@ria-emh2.army.mil (Mark D. McKamey IM SA) writes:
>by Purdue University.  What I am looking for is a detailed comparision
>between SCCS and RCS.  Any information concerning such comparison would be
>greatly appreciated.  Thank You,

One of the things I like most about RCS is that it can collapse
keywords when checking in revisions.  This way, if I forget to check
out a file for locking, then I edit it, I can still check it in
without losing the keywords.

For example, in SCCS, a "%Z%" gets expanded into "@(#)" when checked
out (for compiling), but it cannot collapse that back to "%Z%" if I
check that version in.  In RCS, a "$Id: $" gets expanded to "$Id:
whatever $", which can be collapsed back to "$Id: $" when checked in.

This also makes distribution and updates much easier.  This was very
important in making our decision to use RCS.
 
.... Erik
-- 
Erik Murrey                            /|   //  /~~~~/  |  /
MPX Data Systems, Inc.                / | / /  /____/   |/
erik@mpx.com                         /  /  /  /        /|  Data Systems, Inc. 
{vu-vlsi, bpa, cbmvax}!mpx1!erik    /     /  /       /  |====================