Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

2022-08-02 Thread Michael Opdenacker via lists.openembedded.org
On 8/2/22 10:13, Michael Opdenacker via lists.openembedded.org wrote: Greetings, Exactly. I filed a bug about this last year but I don't know how to fix it. In a few words, I'd like to add "Supported until MM/" to the description of each supported release. This could help peopl

Re: [Openembedded-architecture] should oe-core issue a warning when it reaches EOL?

2022-08-02 Thread Michael Opdenacker via lists.openembedded.org
Greetings, On 8/2/22 09:33, Mikko Rapeli wrote: Hi, On Tue, Aug 02, 2022 at 08:18:46AM +0200, Philip Balister wrote: We are trying to use technology to solve a social problem. No amount of tweaking the code will stop people from making poor choices. How can we do a better job of

[Openembedded-architecture] Removing meta-gplv2 from release notes?

2022-08-03 Thread Michael Opdenacker via lists.openembedded.org
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 release notes. See https://lists.openembedded.org/g/openembedded-architecture/message/1606

Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype

2023-12-01 Thread Michael Opdenacker via lists.openembedded.org
Hi Mark On 24.11.23 at 17:01, Mark Hatle wrote: In the past, the statement was made that we would generate source packages that would include the full source (as referenced in the ${S} directory of the build), but there was no promise that a 'source package' would build, using the tooling of

Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype

2023-12-01 Thread Michael Opdenacker via lists.openembedded.org
Greetings, On 23.11.23 at 15:02, Bruce Ashfield wrote: On Thu, Nov 23, 2023 at 3:51 AM Alexander Kanavin wrote: On Wed, 22 Nov 2023 at 21:04, Michael Opdenacker via lists.openembedded.org wrote: The first prototype would only target the below architectures: - "genericx86-64" ar

Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype

2023-12-01 Thread Michael Opdenacker via lists.openembedded.org
Hi Mark On 24.11.23 at 17:20, Mark Hatle wrote: In the past, the statement was made that we would generate source packages that would include the full source (as referenced in the ${S} directory of the build), but there was no promise that a 'source package' would build, using the tooling

Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype

2023-11-24 Thread Michael Opdenacker via lists.openembedded.org
Alex, Bruce On 23.11.23 at 14:54, Bruce Ashfield wrote: On Thu, Nov 23, 2023 at 4:02 AM Alexander Kanavin wrote: On Wed, 22 Nov 2023 at 21:04, Michael Opdenacker via lists.openembedded.org wrote: - Beginner use case: begin by fetching a binary image, ready to boot on a target machine

Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype

2023-11-24 Thread Michael Opdenacker via lists.openembedded.org
Hi Joshua On 24.11.23 at 16:44, Joshua Watt wrote: While we have the information about each recipe and package that is built in the SPDX document, the process of creating the document has to happen after do_package so that we know what files are actual in each package. As such, it's not

[Openembedded-architecture] Scope of a Yocto binary distribution prototype

2023-11-22 Thread Michael Opdenacker via lists.openembedded.org
Greetings, The Yocto Project has received funding for developing the processes and tooling for enabling binary distributions. As part of that, the project would need some form of prototype test binary distro to develop and test this. The main goal of this would be to develop the tools, and

Re: [yocto] [Openembedded-architecture] New mailing list for layer patches

2024-04-03 Thread Michael Opdenacker via lists.openembedded.org
Hi Paul, On 4/2/24 at 10:38, Paul Barker wrote: On 28/03/2024 14:36, Ross Burton wrote: Hi, At the moment if a layer doesn’t have enough volume to justify a dedicated mailing list for patches (see, for example, meta-...@lists.yoctoproject.org ) then

Re: [Openembedded-architecture] [docs] WOKRDIR change transition guide/notes

2024-05-23 Thread Michael Opdenacker via lists.openembedded.org
Hi Richard, On 5/15/24 at 15:12, Richard Purdie wrote: Now that there is a roughly ready patchset for this I wanted to write down a quick guide to converting recipes. S = ${WORKDIR} == If a recipe has S set to be WORKDIR this is no longer supported. Currently you'll see warnings,