Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!cornell!uw-beaver!tektronix!tekgen!tektools!jerryp
From: jerryp@tektools.TEK.COM (Milan Moncilovich)
Newsgroups: comp.unix.wizards
Subject: Re: RCS vs. SCCS and make (using RCS subdirectories with make)
Message-ID: <2520@tektools.TEK.COM>
Date: Sun, 21-Jun-87 10:07:30 EDT
Article-I.D.: tektools.2520
Posted: Sun Jun 21 10:07:30 1987
Date-Received: Tue, 23-Jun-87 01:17:02 EDT
References: <41@esosun.UUCP> <20393@sun.uucp> <42@loki.esosun.UUCP> <2615@ncoast.UUCP>
Reply-To: jerryp@tektools.TEK.COM (Jerry Peek)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 26

In article <2615@ncoast.UUCP> allbery@ncoast.UUCP (Brandon Allbery) writes:
>As quoted from <42@loki.esosun.UUCP> by pete@esosun.UUCP (Pete Ware):
>+---------------
>| I mentioned make because I also wanted to know those systems that I
>| can count on typing "make" and have it retrieve the appropriate files
>| from SCCS/RCS without having to go and check out every file in sight.
>+---------------
>
>Well, if you're willing to forego the RCS directory (TDI's and ncoast's
>versions of SCCS don't have subdirectories, so I never bothered to use
>RCS subdirectories), you can build RCS-handling make dependencies.

If your flavor of make has a .PREFIXES list, you can use RCS subdirectories,
too.  Just add this .PREFIXES list:

	.PREFIXES: ./RCS

Then, if make can't find the RCS (,v) file in the current directory, it'll
look in the ./RCS subdirectory.  Since "co" doesn't mind checking out files
from other directories, this trick works great.

--Jerry Peek
uucp-style:   {allegra,decvax,hplabs,ihnp4,ucbvax}!tektronix!tektools!jerryp
Domain-style: jerryp@tektools.TEK.COM

I don't speak for Tektronix or its employees.