[haiku-development] Re: VOTE: Git or Mercurial (hg) as Haiku's new source control tool

  • From: "Ingo Weinhold" <ingo_weinhold@xxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 10 May 2011 23:18:56 +0200

On Tue, 10 May 2011 22:58:30 +0200 Niels Sascha Reedijk 
<niels.reedijk@xxxxxxxxx> wrote:
> 2011/5/10 Niels Sascha Reedijk <niels.reedijk@xxxxxxxxx>:
> > Hi,
> >
> > 2011/5/10 Ingo Weinhold <ingo_weinhold@xxxxxx>:
> >> On Tue, 10 May 2011 21:15:48 +0200 Niels Sascha Reedijk
> <niels.reedijk@xxxxxxxxx> wrote:
> >>> I don't remember exactly how long our standard voting time would be (7
> >>> days?). Anyway, I miss many names in this threads, so let's suggest we
> >>> run this vote until Saturday 00.00 GMT?
> >>
> >> I don't know about the others, but my vote is still pending, because I
> don't feel I can make an informed decision yet. E.g. the whole revision
> numbers topic has been discussed at some length, but the proposed solutions
> are not optimal and mostly theoretical. I assumed Oliver's recent changes
> were done to be able to actually test some of those theories, which I find an
> excellent idea.
> >
> > Okay, I will play around with the 'hg' get revision number during
> > build. Maybe someone else can try for git.
> I am having trouble finding where the magic happens. Can someone give
> me a pointer?

Assuming you mean retrieving the revision number and injecting it into libroot 
and kernel. That's done by the CopySetHaikuRevision rule (invoked once for each 
file). The and its actions [1] are defined in build/jam/FileRules. The 
set_haiku_revision build tool injects the revision into the files. After 
Oliver's changes it accepts arbitrary strings up to 128 characters in length, 
so you should only need to fiddle with the actions itself.

CU, Ingo

[1] http://dev.haiku-os.org/browser/haiku/trunk/build/jam/FileRules#L334

Other related posts: