Re: Add 3.7 version of linux-libc-headers

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2012-12-11 at 05:52 -0500, Bruce Ashfield wrote:
> On Tue, Dec 11, 2012 at 5:12 AM, Marcin Juszkiewicz
> <marcin.juszkiewicz@linaro.org> wrote:
>         I would like to know are there plans to use 3.7 kernel for
>         libc headers.
>         This will allow me to drop own copy which I need to keep due
>         to AArch64
>         stuff which got added in 3.7 cycle.
>
> There aren't any plans to use 3.7 for the headers, since we are
> tracking the headers
> with the same cadence as the yocto release kernels. Otherwise, we'd
> really need 
> to have all versions available, and keeping things clean and focussed
> was the
> goal.
>
> 3.8 is the next likely update.
>
> That being said,  since the libc-headers version is controlled by the
> LINUXLIBCVERSION in tcmode-default.inc, simply having 3.7 headers
> available shouldn't cause any problems or disconnects. 
>
> So we can open up the discussion if we want to carry extra libc
> headers or
> keep with the current strategy. I've added Richard explicitly to the
> cc' so he
> can jump in as appropriate.
> 
As I understand things we agreed that we'd not bump for point releases
on the headers unless there was some pressing reason too. The rest of
the policy for kernel headers is a bit more fuzzy.

For actual major version increments like this, I'm tempted to accept
that in this case we have a good argument for updating to 3.7 and even
though the linux-yocto kernels will lag behind this for a (short) while,
it shouldn't make any real world difference to anything, certainly not
cause breakage.

There isn't any technical reason we have to keep in lockstep, or any
known issues with doing that with these versions, right? I know you have
been burnt in the past but that was quite a while ago and the
kernel/toolchain communities have moved to address that?

Cheers,

Richard