Re: Misleading RCS behaviour

2001-06-12 Thread Tom Tromey
> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes: Paul> Without GPATH, new files checked out will be placed in the target Paul> directory; with it they will be updated in the source directory. We could add that, but we couldn't rely on it. Well, maybe we could, since really we only suppor

Re: Misleading RCS behaviour

2001-06-10 Thread Paul D. Smith
%% Ben Elliston <[EMAIL PROTECTED]> writes: >> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes: Paul> If you need to have the files created in their VPATH-found location Paul> instead of in the local directly, use the GPATH variable to specify Paul> which directories contain those

Re: Misleading RCS behaviour

2001-06-07 Thread Ben Elliston
> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes: Paul> If you need to have the files created in their VPATH-found location Paul> instead of in the local directly, use the GPATH variable to specify Paul> which directories contain those types of files. Paul> See the GNU make manual

Re: Misleading RCS behaviour

2001-06-07 Thread Paul D. Smith
If you need to have the files created in their VPATH-found location instead of in the local directly, use the GPATH variable to specify which directories contain those types of files. See the GNU make manual, and let me know. I don't think this is the right behavior to make the default, though:

Re: Misleading RCS behaviour

2001-06-07 Thread tom_honermann
<[EMAIL PROTECTED]cc: om> Subject: Misleading RCS behaviour

Misleading RCS behaviour

2001-06-06 Thread Ben Elliston
I have discovered some misleading behaviour in GNU Make. It pertains to the combination of RCS files and VPATH. Here is a Makefile that I have written to demonstrate the problem. Suppose this is a Makefile generated by `configure' -- ie. it resides in the "build tree" (see diagram below).