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

[Michael Smith]

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.

Hi Chris,

If a distro doesn't lock down a particular version of a package, I 
figure after a "git pull" I'll be building the latest version of 
everything. At least, if I do a "bitbake -c clean somepkg" followed by a 
"bitbake somepkg", I'll get the latest version of somepkg.

If I understand the patch correctly, that won't happen anymore unless I 
remember to remove tmp/versions.conf. It adds an extra step to the 
process when one developer is using another's package.

I can see it leading to confusion between developers. Any time there's a 
multi-step process, humans will find a way to forget a step. :)

What's the problem the versions.conf is meant to solve? I would think if 
I'm doing a git pull and then rebuilding a package, it's because I want 
to get the latest version, but I think I'm missing something here.

Mike