public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jan-Simon Moeller <dl9pf@gmx.de>
To: "openembedded-architecture@lists.openembedded.org"
	<openembedded-architecture@lists.openembedded.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: paul@pbarker.dev
Subject: Re: [OE-core] Improving DISTRO_FEATURES backfill & opt-out
Date: Thu, 26 Feb 2026 12:04:14 +0100	[thread overview]
Message-ID: <4855971.vXUDI8C0e8@monster> (raw)
In-Reply-To: <ba0a57bc87f3563f43f46f663e1733fd552a7a03.camel@pbarker.dev>

Hi all,


[...]
> What does that look like practically? Something like this I think:
> 
>     DISTRO_FEATURES_BASELINE = " \
>         acl alsa bluetooth debuginfod ext2 ipv4 ipv6 pcmcia usbgadget \
>         usbhost wifi xattr nfs zeroconf pci 3g nfc x11 vfat seccomp \
>         pulseaudio gobject-introspection-data ldconfig \
>     "
> 
>     DISTRO_FEATURES_DEFAULT = "${@filter_default_features('DISTRO_FEATURES',
> d)}" DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}"
> 
>     DISTRO_FEATURES_OPTOUT ?= "${DISTRO_FEATURES_BACKFILL_CONSIDERED}"
> 
>     def filter_default_features(varname, d):
>         baseline_features = (d.getVar(varname + "_BASELINE") or "").split()
>         optout_features = (d.getVar(varname + "_OPTOUT") or "").split()
> 
>         return [feature for feature in baseline_features \
>                 if feature not in optout_features]
> 

I like the clearer terminology -  +1 .

Best,
Jan-Simon





  reply	other threads:[~2026-02-26 11:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26  9:59 Improving DISTRO_FEATURES backfill & opt-out Paul Barker
2026-02-26 11:04 ` Jan-Simon Moeller [this message]
2026-02-26 12:03 ` [Openembedded-architecture] " Richard Purdie
2026-02-26 14:07   ` Trevor Gamblin
2026-02-26 20:31     ` [OE-core] " Ankur Tyagi

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=4855971.vXUDI8C0e8@monster \
    --to=dl9pf@gmx.de \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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