gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: tagline robustness


From: Andrew Suffield
Subject: Re: [Gnu-arch-users] Re: tagline robustness
Date: Sat, 23 Aug 2003 18:32:14 +0100
User-agent: Mutt/1.5.4i

On Sat, Aug 23, 2003 at 05:40:02PM +0100, Bruce Stephens wrote:
> wave++ <address@hidden> writes:
> >> I suggest that it could be better and safer if arch tag had a form
> >> similar to RCS tag ($Id$, $Header$, etc.).  Even though RCS tags
> >> have different purposes, their format should be taken by arch tags.
> >> In this case arch tags will look like:
> >> 
> >>    For a C file:
> >> 
> >>      /* $Arch: 53bb84c6-dee0-46c6-a275-2db144993d89$ */
> >>    or
> >>      static char archid[] = "$Arch: 53bb84c6-dee0-46c6-a275-2db144993d89$";
> >
> > It would be nice to support different separators besides
> > "$". Actually $ breaks many scripting languages and imposes that you
> > should be able to disable it in this case.
> 
> As has probably been pointed out, this is likely to be useless.  In
> RCS, things like $Id$ are useful because they change, so doing "ident"
> on binaries tells you something useful about the source from which
> they were built.  But in arch, the tag almost certainly doesn't tell
> you anything that you didn't already know, so being able to embed it
> in binaries isn't useful.  As far as I can see, anyway.  

It's downright dangerous. tla might pick up the tag and think it's a
different version of the file.

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

Attachment: pgptfAPt8suX7.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]