[oe] [RFC] Partial merge of SRCPV

Koen Kooi k.kooi at student.utwente.nl
Fri Apr 16 08:36:11 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16-04-10 10:17, Martin Jansa wrote:
> On Tue, Apr 13, 2010 at 1:23 PM, Martin Jansa <martin.jansa at gmail.com> wrote:
>> Please consider applying this patch series.
>>
>> Proposed and discussed in [1], the main reason for NACK (multiple builders
>> uploading to shared feeds) was resolved with bitbake patch [2] and it's
>> enabled by default in PATCH 1/6. It needs bitbake 1.10 or master, but Koen
>> confirmed yesterday that he is using 1.10 already.
>>
>> People not using multiple builders or any of changed recipes don't need to
>> upgrade their bitbake, just keep your tmp/cache dir even for rebuilds from
>> scratch (as you already should, if you have ever used AUTOREV).
>>
>> I'll keep SRCPV changes for other recipes in shr/unstable branch so maintainers
>> of other recipes can move to SRCPV easily too.
>>
>> WARNING: don't use BB_LOCALCOUNT_OVERRIDE with AUTOREV, it will make revision
>> counter in PV constant and chaning SRCREV is not enough to ensure increasing PV.
>>
>> [1] : http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg01325.html
>> [2] : http://git.openembedded.org/cgit.cgi/bitbake/commit/?h=1.10&id=2f32735463159e9e42e03819d6b505dba49c7f17
> 
> No comment?
> 
> if nobody care then maybe we can push it even without
> BB_LOCALCOUNT_OVERRIDE enabled by default.
> It will be closer to current state and whoever needs it, can enable it
> for his local.conf or distro easily,
> without forcing AUTOREV people to enable it imediately after this push.

BB_LOCALCOUNT_OVERRIDE should be enabled by default, autorev people are
used to breakage.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLyCF7MkyGM64RGpERAqHPAJ4tD39hWTXCXmWcQQP5vBsqtpRObACfb9U7
H7tCZ4pDFGejbBj8lTXqgxQ=
=b58J
-----END PGP SIGNATURE-----





More information about the Openembedded-devel mailing list