SRCREV and git packages

Rod Whitby rod at
Mon May 12 07:49:00 CEST 2008

In what timezone is SRCDATE defined, and what happens when a build crossed midnight in that timezone?
I thought SRCDATE was deprecated compared to SRCREV for these reasons?
-- Rod

-----Original Message-----
From: John Lee <john_lee at>
Date: Monday, May 12, 2008 1:54 pm
Subject: Re: SRCREV and git packages
To: Holger Freyther <zecke at>
CC: distro-devel at

On Sun, May 11, 2008 at 08:20:56PM +0200, Holger Freyther wrote:
> Hey,
> we, as in Openmoko, have preferred SRCDATE for git based recipes over SRCREV 
> for one simple reason. We need an increasing number for the package version 
> and for git we made a number up and stored it within the tmp directory. 
> Removing the tmp directory removed that numbers and we had new packages going 
> back.
> To partially avoid this issue. Get the latest Bitbake from the bitbake-1.8 
> branch and put something like this [1] into your local.conf. This will put 
> the persistent data into your home directory and you can wipe the tmp dir 
> without losing this. Another approach is coming soon as well.
>Actually I use SRCDATE in openmoko-linux because I want a increasing number even across different repositories.  The persistent data is
>specific to the build machine so I decided not to use that.

More information about the distro-devel mailing list