On Thu, 18 Aug 2022 at 11:27, Richard Purdie <richard.purdie@...> wrote: > The intent is the user could add something like: > > require conf/yocto-autobuilder/x32.inc > > or > > require conf/yocto-aut

lists.openembedded.org wrote: I've gone ahead and sent some patches for this for OE-Core and BitBake. There is more work to do so if anyone has a few minutes and wants to clean up a few more file head

Hi all, Today I’m excited to publish a tool I’ve been developing internally for about a year now. It is called ‘yb’, and you can think of it like a cross between kas, Google’s repo, and myrepos (mr).

Hello, an idea just popped into my head that I don't remember having been discussed: Should stable-branch oe-core issue a warning via bitbake when it is close to EOL and perhaps a stronger warning whe

Hi Lee Thanks for the milestone release! Have you seen the discussion on the Openembedded-architecture mailing list? It seems there's a consensus to drop meta-gplv2 from master, and also from the rele

meta-gplv2 makes the TSCs very nervous (certainly YP and I believe OE TSC people too although it hasn't had an official discussion there). It has a load of old "pre GPLv3 license" versions of software

I've been asked about my thoughts on the eSDK. I'm going to try and write down some of my ideas and thinking about it. I don't have a fully thought out plan to pull off the shelf but can at least shar

On Wed, 20 Jul 2022 at 17:46, Alexander Kanavin via lists.yoctoproject.org <alex.kanavin=gmail.com@...> wrote: Which I just resent. Now we have confirmation from Intel that nobody minds reducing the s

Note: this update fails on x32 with | configure: error: unrecognized GNU build triplet linux-gnux32 This time I want to put my foot down and suggest that we just drop the whole x32 variant from the au

Thanks to everyone that replies and especially to people helping get answers from outside our developer bubble. See the attached pdf. Philip

I've been worrying about license and copyright information in our codebase for a while. We're slowly getting there with license info and scripts have good information now. We still need to work out li

On Wed, 29 Jun 2022 at 11:33, Alexander Kanavin via lists.openembedded.org <alex.kanavin=gmail.com@...> wrote: > I'm now prototyping the other missing piece for the 'direct SDK > workflow', which is l

At today's Yocto Project Technical Team Meeting Armin raised a question about the proper way to set up local.conf to use the Yocto Project state mirror for dunfell. This email is intended to bring tho

I've gone around in circles on this for a long time. The background isn't obvious at first glance. "S" represents where our source is. There is code like do_unpack which wants to clean S before rerunn

We are finalizing the agenda for the developer meeting this Friday (May 20). The agenda has some topics carried from prior meetings and some new ideas we will cover at the bottom. We would like to get

Folks, For those of us who have had to work on GO recipes I think there has been an open item that would be nice to get resolved in this new release cycle. Specifically, as with many of the modern lan

There will be an OpenEmbedded Developer Virtual Meeting (OEDVM) held on Friday, 20 May 2022. This will be the day after the Yocto Project® Summit 2022.05 concludes. The scheduled time will match the Y

Hi Richard and Joshua, When using hash equivalency, since commits https://git.openembedded.org/openembedded-core/commit/?id=d6c7b9f4f0e https://git.openembedded.org/openembedded-core/commit/?id=1cf628

For many months a small group of people have tried to get our automated testing to the point where we can make builds with reliable test results. We hold the project to a high standard and the TSC (ri

Hi All, There are a few different discussions I'd like to pull together and talk about some QA and release process changes. Firstly, we've just made some changes to the docs build process. This is now