[ On Thursday, March 16, 2000 at 10:14:44 (-0600), Andy Glew wrote: ]
> Subject: Re: CVS keywords and make
>
> Laird: I think that your question is of general interest,
> so I am replying to the mailing list.
>
> The problem is that step (4) modifies the RCS/CVS keywords,
> even if nothing else in the file is modified. Leading to
>
> (5) Unnecessary remake of the file
> (and all files that depend on it)
>
> when I repeat the process.
That step is not "unnecessary" given the tools that you are using.
If you don't want the "unnecessary" recompiles then you have to either
use a smarter build system (an incremental compiler in an IDE, for
example); or stop using RCS keywords in your source files.
Back-dating the file on commit (i.e. when the update is done to retrieve
the new keyword values) is definitely not possible (i.e. is wrong) as a
general solution.
You can of course be much more selective about when keywords are
expanded too. You could use '-ko' (which will be "sticky" in the CVS
sense if set on checkout), or perhaps '-kk' (which I think will also
become "sticky" on checkout). Then when you make a release with "cvs
export" you would use '-kv' to freeze the current values of the keywords
into your files for the actual release.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
