Re: [OE-core] [PATCH] u-boot: set git repo branch with SRCBRANCH

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Mon, Apr 07, 2025 at 07:05:54PM +0200, Alexander Kanavin wrote:
> On Fri, 4 Apr 2025 at 09:51, Mikko Rapeli via lists.openembedded.org
> <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
> >
> > Enables changing branch from "master" to "next"
> > when building bleeding edge upstream versions for
> > testing purposes. Now local.conf setup to
> > build latest "next" version becomes:
> >
> > INHERIT += "poky-bleeding"
> > POKY_AUTOREV_RECIPES += "u-boot"
> > SRCBRANCH:pn-u-boot = "next"
> 
> But 'next' is not a bleeding edge branch. It's a fluid, and probably
> forced-pushed-to testing branch which is not even on top of master,
> but rather master has commits that next does not:
> 
> https://source.denx.de/u-boot/u-boot/-/branches
> 
> Is there a use case for using it in yocto builds?

Yes, testing features which are queued to merging but this process is taking
quite some time. If "yocto builds" is your oe-core/poky CI builds then I
think it's a no, no uses. But for me, I care about u-boot, tf-a, optee etc
and want to build their 'next' and master branches from time to time
to test features which are being merged. For example optee support for some new
HW or u-boot pmem support to boot memory based OS images.

FWIW, upstream optee developers use buildroot integration setup for similar
things and I have a need to use yocto based one.

> Another problem is that this sets a precedent we'd rather not set. If
> you want to tweak bits of SRC_URI, it's better to just reset the whole
> thing.

SRC_URI contains more than just SCM URIs and I don't want to overwrite
them. For example all the config snippets and patches. I'm also interested
if patches no longer apply and/or break builds. So I really just want to change
the upstream SCMs to different branch.

A lot of recipes do this already in oe-core so I though it would not be
a big deal for you.

Cheers,

-Mikko