Hi,
The problem with 4.8 is that because of the constant rebasing in the
downstream, it will get broken fast.
So someone will have to maintain it and constantly update it, and if we don't
do it for master, it's unlikely to be done on Morty.
At some point, 4.8 will stop changing, but we're not there yet.
Right now, 4.4 is stable in downstream, and it seems 4.7 is also - at least
4.7.10 compiles.
If we don't want to keep 4.7 in Morty, the best bet is probably 4.4 + 4.9,
knowing there'll be a lot of updates in 4.9 - but they'll follow the ones in
master.
Cheers,
Herve
> On 19 Jan 2017, at 20:55, Andrei Gherzan <and...@gherzan.ro> wrote:
>
>> On Thu, Jan 19, 2017 at 12:41 PM, Paul Barker <p...@paulbarker.me.uk> wrote:
>>> On 19 January 2017 12:07:11 GMT+00:00, Andrei Gherzan <and...@gherzan.ro>
>>> wrote:
>>> On Thu, Jan 19, 2017 at 12:03 PM, Paul Barker <p...@paulbarker.me.uk>
>>> wrote:
>>>> On 19 January 2017 11:50:57 GMT+00:00, Andrei Gherzan
>>> <and...@gherzan.ro> wrote:
>>>>> From: Paul Barker <p...@paulbarker.me.uk>
>>>>>
>>>>> Signed-off-by: Paul Barker <p...@paulbarker.me.uk>
>>>>> ---
>>>>> recipes-kernel/linux/linux-raspberrypi_4.8.bb | 8 --------
>>>>> 1 file changed, 8 deletions(-)
>>>>> delete mode 100644 recipes-kernel/linux/linux-raspberrypi_4.8.bb
>>>>>
>>>>> diff --git a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
>>>>> b/recipes-kernel/linux/linux-raspberrypi_4.8.bb
>>>>> deleted file mode 100644
>>>>> index be25e65..0000000
>>>>> --- a/recipes-kernel/linux/linux-raspberrypi_4.8.bb
>>>>> +++ /dev/null
>>>>> @@ -1,8 +0,0 @@
>>>>> -FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>>>>> -
>>>>> -LINUX_VERSION ?= "4.8.16"
>>>>> -
>>>>> -SRCREV = "061dccce6cf6705bbb5da29a643f4b0ad1d11630"
>>>>> -SRC_URI =
>>>>> "git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.8.y
>>> \
>>>>> -"
>>>>> -require linux-raspberrypi.inc
>>>>
>>>> I'm not sure on this one. I don't think we should drop kernel
>>> versions from a stable branch unless they're broken. Can we hold off on
>>> this and I'll have a look at it tomorrow.
>>>>
>>>> (Resending as I mis-clicked and didn't do reply all)
>>>
>>> I don't see the benefit in keeping 4.8 and 4.9. The default + the
>>> latest should be enough. Default would give stability and suitable for
>>> production while latest will give new features.
>>>
>>> BTW I already removed 4.8 from master.
>>>
>>
>> Agreed for master. I'm just wondering if we want to leave 4.8 on morty (if
>> it currently builds) in case anyone depends on that version.
>>
>> I can see the other side though - if you need a stable branch of
>> openembedded you should probably also use a linux-raspberrypi version that's
>> stable.
>
> I'll try to compile and not remove it if it compiles. Doesn't hurt to
> leave it there anyway.
>
> --
> Andrei Gherzan
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
