Re: Patch to gcc_update to include revision number in LAST_UPDATED

[Mike Stump <mrs at apple dot com>]

On Oct 31, 2005, at 7:46 PM, Daniel Berlin wrote:
> On Mon, 2005-10-31 at 19:18 -0800, Mike Stump wrote:
> > I wanted to use a subversion substitution tag on version.c, but,  
> > that didn't do what I wanted.  I tried $Rev$ in version.c, the  
> > problem was it never updated,
>
> Right.
> It's really LastChangedRev.

?  I tried it, it doesn't work (from the manual):

  LastChangedRevision
  This keyword describes the last known revision in which this file  
changed

  in the repository, and looks something like $LastChangedRevision:  
144 $.

  It may be abbreviated as Revision or Rev.

Notice how it is misspelled at best, and exactly identical to what I  
already tried and didn't work at worst.

> > unless I modified version.c itself.  What I would like is a way  
> > for co/update/
> > export to get the revision number automatically for use in version.c.
>
> svnversion . >> version.c

I wanted it for svn export as well.  The problem is, the svnness is  
stripped by export, so post that time, we can't run svnversion.  I'd  
love a keyword that is updated and reflects the '^Revision:' line  
from svn info of the file, and is resubstituted each time the file is  
updated/exported.  I don't want the '^Last Changed Rev:' line, which  
appears to be what $Rev$ does.

Now, why, why do I want this, so that in version.c we can put the  
name of the svn branch and the svn revision number, and have that be  
enough to always get the software, with the exception that  
independently updated files aren't going to be accurate, only whole  
tree updates will be accurate.  This might allow us to then use that  
as a tracking mechanism instead of the apple-gcc-5245 style tags we  
currently use.

Our production builds do an export to get the software as the first  
step.