public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] sstate/sstatesig: Abstract dummy package architectures into layer.conf settings
Date: Tue, 17 Mar 2026 08:22:13 +0000	[thread overview]
Message-ID: <e69ed8a6abe51f1bca2779f24edfa9d9e4d23d01.camel@linuxfoundation.org> (raw)
In-Reply-To: <DB5PR02MB102139B16A3C8B755F94EFCD8EF40A@DB5PR02MB10213.eurprd02.prod.outlook.com>

On Mon, 2026-03-16 at 13:03 +0000, Peter Kjellerstedt wrote:
> > > Wouldn't it be more appropriate to use += for these two?
> > > Otherwise one will have to use :append to add to them in other
> > > layers.
> > 
> > That depends on whether your layer is included after core or not.
> > I'd have thought including before core would be potentially
> > problematic anyway...
> 
> Sure, but with += the order does not matter.
> 
> We have "meta" as the last layer in BBLAYERS in our setup. E.g., 
> these are the external layers I have in one of our configurations:
> 
> BBLAYERS ?= " \
>   ...
>   .../meta-virtualization \
>   .../meta-webserver \
>   .../meta-multimedia \
>   .../meta-filesystems \
>   .../meta-networking \
>   .../meta-python \
>   .../meta-oe \
>   .../meta-poky \
>   .../meta \
> "
> 
> We have them configured like this to as best as possible match the 
> layer priorities. It is not perfect (e.g., meta-poky prepends to 
> BBPATH instead of appending like all the other layers do), but it 
> has resulted in the least surprises regarding things that are based 
> on BBPATH and things that are based on layer priorities.

We need to rewrite how this all works and remove some of the options as
it is all too complex and everyone is putting it together differently
and hoping for the best :(.

Trying to "support" the number of possible combinations that people
might put things together is problematic. The ask is that everything
works regardless of how you configure it and nobody even
understands/agrees on the basic rules.

If you don't understand my concern, think about how you'd recreate that
setup just starting from core and using bitbake-layers add-layer. I
don't think you can.

It is too late to do anything about it right now and I've put off
trying to improve things as I know the shear amount of complaints I'll
get but there is a problem here.

Cheers,

Richard


  reply	other threads:[~2026-03-17  8:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-14 10:27 [PATCH] sstate/sstatesig: Abstract dummy package architectures into layer.conf settings Richard Purdie
2026-03-14 10:45 ` Patchtest results for " patchtest
2026-03-16 11:21 ` [OE-core] " Peter Kjellerstedt
2026-03-16 11:28   ` Richard Purdie
2026-03-16 13:03     ` Peter Kjellerstedt
2026-03-17  8:22       ` Richard Purdie [this message]
2026-03-17 17:41         ` Peter Kjellerstedt
2026-03-17 20:39           ` Richard Purdie

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=e69ed8a6abe51f1bca2779f24edfa9d9e4d23d01.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    /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