Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!van-bc!dds4!wolfe
From: wolfe@dds4.uucp (Peter Wolfe)
Newsgroups: comp.software-eng
Subject: Re: CVS-RCS
Message-ID: <1991May23.201749.20336@dds4.uucp>
Date: 23 May 91 20:17:49 GMT
References: <1991May21.135016.3671@apertus.uucp>
Organization: Digital Dispatch Systems, Richmond BC
Lines: 25

In article <1991May21.135016.3671@apertus.uucp> apertus!ivanp@tenfwd.uci.com writes:
>I am looking over CVS, a system that is a add on to RCS (a configuration
>management system) and I have a question I hope someone would please answer:
>
>How does CVS support (or does CVS support) dual derivations?
>

This is a topic worth doing some surveys on.  Come on folks - how do you
take care of multiple derviations of common source using CVS/RCS/SCCS (I
know that you can throw money at Configuration Management vendors to do
this).

In a past life I cobbled together massive CSH/SCCS scripts to support
this.  Each release had a directory tree and a configuration file
indicating which version (R.L.B.S or R.L) it was using.  The sccs get
command would use the R or R.L.B to fetch the latest copy.  You could
link releases together so that changes to common source would propogate.

One distinction between SCCS and RCS is the time when you indicate what
version you wish to checkin.  SCCS requires you to identify at checkout
time the version (e.g. a new branch) you are creating while RCS only
allows this at checkin time.
-- 
Peter Wolfe (604-270-1171) uunet!van-bc!dds4!wolfe
Digital Dispatch Systems, Richmond BC Canada