From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org,
Joshua Watt <JPEWhacker@gmail.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Subject: Re: [OE-core] [PATCH 4/5] meta/dummy-sdk-package: Improve SDK dummy package handling
Date: Sat, 14 Mar 2026 10:28:26 +0000 [thread overview]
Message-ID: <e116990c00b33a1bf02da5b45707f3b48a5cc9f9.camel@linuxfoundation.org> (raw)
In-Reply-To: <189CACDC59FF3062.2629287@lists.openembedded.org>
On Sat, 2026-03-14 at 10:00 +0000, Richard Purdie via lists.openembedded.org wrote:
> Options could be:
>
> a) move the recipe to core and add another entry to
> sstate.bbclass/sstatesig.py . That doesn't help it anyone else does
> this
>
> b) Create some layer.conf variables which allow these to be
> defined/added generically. That would need careful manipulation of the
> hash variable dependencies to stop things rebuilding like crazy.
Having said this all out loud, b) is the only realistic option so I've
just sent a patch which does that. I don't like it but it is the least
worst option I can see right now.
Cheers,
Richard
next prev parent reply other threads:[~2026-03-14 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 9:47 [PATCH 1/5] sstate: Drop unneeded SSTATE_MANMACH variable Richard Purdie
2026-03-14 9:47 ` [PATCH 2/5] bitbake.conf: Add SDKMACHINE to BUILDCFG_VARS, drop TARGET_FPU Richard Purdie
2026-03-16 16:37 ` [OE-core] " Alejandro Hernandez
2026-03-16 21:01 ` Richard Purdie
2026-03-14 9:47 ` [PATCH 3/5] allarch/lib: Convert core of allarch code into a function Richard Purdie
2026-03-14 9:47 ` [PATCH 4/5] meta/dummy-sdk-package: Improve SDK dummy package handling Richard Purdie
2026-03-15 14:08 ` [OE-core] " Mathieu Dubois-Briand
2026-03-14 9:47 ` [PATCH 5/5] sstate: Tweak SDK sstate package architecture Richard Purdie
[not found] ` <189CAC32AB5A06DA.1508127@lists.openembedded.org>
2026-03-14 10:00 ` [OE-core] [PATCH 4/5] meta/dummy-sdk-package: Improve SDK dummy package handling Richard Purdie
2026-03-14 14:40 ` Bruce Ashfield
[not found] ` <189CACDC59FF3062.2629287@lists.openembedded.org>
2026-03-14 10:28 ` Richard Purdie [this message]
2026-03-16 16:37 ` Randy MacLeod
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e116990c00b33a1bf02da5b45707f3b48a5cc9f9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=JPEWhacker@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox