[OE-core] [PATCH 0/3] linux-libc-headers: 3.2 and linux-libc-headers-yocto movement

Bruce Ashfield bruce.ashfield at gmail.com
Fri Mar 23 17:45:48 UTC 2012


On Fri, Mar 23, 2012 at 1:22 PM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>
> Op 23 mrt. 2012, om 18:07 heeft Bruce Ashfield het volgende geschreven:
>
>> Richard/Saul,
>>
>> As discussed on the mailing list here is a libc-headers series. I've kept it in
>> three parts so you can pick what you want (except for the minor detail of
>> needing to split patch 1/1 to keep 3.1 around if you don't want 2/3).
>>
>> I've built and booted this on all the emulated targets, and have some other
>> builds running against larger numbers of packages as well.
>>
>> Cheers,
>>
>> Bruce
>>
>> The following changes since commit bb1d7fad7ff8515939f2b5f0b540b9b09604be3c:
>>  Richard Purdie (1):
>>        Revert "bitbake.conf/sstate.bbclass: Change PATH when installing sstate files to avoid issues"
>>
>> are available in the git repository at:
>>
>>  git://git.pokylinux.org/poky-contrib zedd/libc-headers-oe
>>  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/libc-headers-oe
>>
>> Bruce Ashfield (3):
>>  linux-libc-headers: add 3.2 headers and remove 3.1
>>  linux-libc-headers: set default LINUXLIBCVERSION to 3.2
>>  linux-libc-headers-yocto: remove from oe-core
>
> Would it make more sense to move to 3.3 or is that too risky at this point? I'm fine with the patchset either way, though.

I thought about it as well, but since I've been building a booting 3.2 more
often than 3.3, I took it easy with this change.

But a 3.3/3.4 bump makes sense in the not too distant future, and obviously
if there's consensus, I wouldn't argue strenuously against 3.3.

Cheers,

Bruce



>
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"




More information about the Openembedded-core mailing list