[yocto] ***SPAM*** Re: [meta-raspberrypi] Current master broken

[Trevor Woerner]

On Tue 2016-12-06 @ 11:00:34 PM, Paul Barker wrote:
> Upstream effectively support one version, currently 4.4. When upstream
> made that the default branch, the changes to the 4.1 branch stopped -
> there wasn't really much overlap. Everything post-4.4 is active
> development and gets rebased at will. At some point they'll move to the
> next LTS release (4.9) and 4.4 will be dropped.

Are you speaking specifically about the kernel for raspberry pi, or in
general? Because the kernel for raspberry pi has several branches that are all
maintained and kept up-to-date. It's actually quite commendable how this
repository is maintained. Branches for 4.4, 4.7, 4.8, 4.9 and others are all
usable (ignoring the constant rebasing thing...)

> I'd class all recipes for kernel versions other than default branch
> upstream as experimental. Perhaps we should just go with AUTOREV here?
> Anything else is going to need changing really often.

Not every revision of those branches are usable for raspberry pi. Someone
named "popcornmix" has been keeping everything aligned with upstream, and
merging in the support for raspberry pi.

If you took the rpi-4.8.y branch, for example, and happened to check out
commit 356ccf6d2b0cfe9dca6c5d961bfd04dc8c0f4e64, you wouldn't have something
that would build.

The problem is they keep rebasing, which messes up the SRC_URIs :-(