Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!swrinde!ucsd!helios.ee.lbl.gov!pasteur!ucbvax!agate!violet.berkeley.edu!ilan343
From: ilan343@violet.berkeley.edu
Newsgroups: comp.unix.questions
Subject: RCS and multiple modules
Summary: How do I use RCS with  multiple module software?
Message-ID: <1990Mar6.195640.26473@agate.berkeley.edu>
Date: 6 Mar 90 19:56:40 GMT
References: <22675@adm.BRL.MIL>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Organization: University of California, Berkeley
Lines: 16

I have been using RCS to keep track of changes to software involving a
large number of modules (30-40).  I am looking for suggestions on how
to organize the releases of the complete software configuration.

How do I treat the whole package as a single unit?

I'd like to give it a revision name( or number in the X.XX.XX format).
Also, I'd like use this name inside the code, as I can with keywords
like $Header$ for each individual module.

I know of "symbolic names", but they seem somewhat inflexible. From
what I understand, the symbolic names are associated to just the
revision number itself, but not to the level number, or branches.

Any comments on how to effectively use RCS (or other revision control
packages) would be appreciated.