[oe] [PATCH] bitbake.conf, freeze.inc: Add version lockdown implementation and use it by default.

[Denys Dmytriyenko]

On Wed, May 13, 2009 at 05:25:46PM -0400, Denys Dmytriyenko wrote:
> On Wed, May 13, 2009 at 01:53:18PM -0700, Chris Larson wrote:
> > For each recipe which completes a task successfully, this emits the current
> > version into ${TMPDIR}/versions.conf as a PREFERRED_VERSION line.
> > ${TMPDIR}/versions.conf and conf/versions.conf are automatically included,
> > in that order, in subsequent builds, to provide more deterinistic builds by
> > default, and to let the user make the lockdown persist via a simple cp
> > command.
> > 
> > Assuming that the latest ncurses in the recipes is 5.7, and that 5.7 is
> > preferred over 5.3 by default given any distro version preferences, if they
> > exist, the following are examples of its behavior:
> > 
> > $ rm -rf tmp
> > $ bitbake ncurses-5.3
> > $ bitbake -c clean ncurses
> > $ bitbake ncurses # builds ncurses 5.3
> > 
> > $ cp tmp/versions.conf conf/
> > $ rm -rf tmp
> > $ bitbake ncurses # builds ncurses 5.3
> 
> Very nice! Let me try it here...
> 
> > Signed-off-by: Chris Larson <clarson at mvista.com>

Chris,

Will you be sending an updated version of the patch, which handles TMPDIR 
overwritten in local.conf, as we discussed last week? Thanks.

-- 
Denys