Re: [Gnu-arch-users] stamping files with revision id's.

[Andrew Suffield]

On Mon, Oct 20, 2003 at 07:11:12AM +1000, Robert Collins wrote:
> > In almost all cases, your approach will add spurious conflicts if you
> > merge from several branches where this feature is used.  Maybe you can
> > use something else to construct the data you need?
> 
> There are alternatives: =REVISION-ID in configs for instance. The useful
> thing about inline revision details is that you can compile them into
> runtime debug output.

I have pondered this in the past, and concluded that it's actually a
set of distinct problems that should be solved in different ways.

To embed the revision data in debug output, don't do it at commit time
- do it at build time. Put $(shell tla logs -f | tail -n 1) into
CFLAGS or generate a C header or something. If you're using automake,
write a rule to generate a header and put that header into
noinst_HEADERS so it gets build and included in distribution
tarballs.

I expect we can think up similar sorts of solutions for other problems
that in CVS are solved with $Id $.

-- 
  .''`.  ** Debian GNU/Linux ** | Andrew Suffield
 : :' :  http://www.debian.org/ |
 `. `'                          |
   `-             -><-          |

signature.asc
Description: Digital signature