From: Ross Burton <Ross.Burton@arm.com>
To: "changqing.li@windriver.com" <changqing.li@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH V2] appstream: upgrade from 1.0.6 to 1.1.2
Date: Tue, 10 Mar 2026 11:44:18 +0000 [thread overview]
Message-ID: <C0CE5EB9-AB4B-40D5-B625-3C34119E3099@arm.com> (raw)
In-Reply-To: <20260225034013.1510432-1-changqing.li@windriver.com>
On 25 Feb 2026, at 03:40, Changqing Li via lists.openembedded.org <changqing.li=windriver.com@lists.openembedded.org> wrote:
> PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}"
> +PACKAGECONFIG:append:class-target = " bash-completion"
>
> PACKAGECONFIG[systemd] = "-Dsystemd=true,-Dsystemd=false,systemd"
> PACKAGECONFIG[stemming] = "-Dstemming=true,-Dstemming=false,libstemmer"
> PACKAGECONFIG[qt6] = "-Dqt=true,-Dqt=false,qtbase"
> +PACKAGECONFIG[bash-completion] = "-Dbash-completion=true,-Dbash-completion=false”
I can’t see any other recipes that have a PACKAGECONFIG for bash completion. Personally I’d just inherit the class and EXTRA_OEMESON:append:class-native = “ -Dbash-completion=false” as the special case is native.
Ross
next prev parent reply other threads:[~2026-03-10 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:41 [PATCH 1/2] libfyaml: init add Changqing Li
2026-02-24 1:41 ` [PATCH 2/2] appstream: upgrade from 1.0.6 to 1.1.2 Changqing Li
2026-02-24 9:58 ` [OE-core] " Alexander Kanavin
2026-02-24 15:44 ` Peter Kjellerstedt
2026-02-25 3:28 ` Changqing Li
2026-02-25 3:40 ` [PATCH V2] " Changqing Li
2026-03-10 11:44 ` Ross Burton [this message]
2026-03-11 2:27 ` [OE-core] " Changqing Li
[not found] ` <189BA872138654D8.2412760@lists.openembedded.org>
2026-03-13 2:30 ` Changqing Li
[not found] ` <18976046C73DA293.1454197@lists.openembedded.org>
2026-02-25 4:39 ` Changqing Li
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=C0CE5EB9-AB4B-40D5-B625-3C34119E3099@arm.com \
--to=ross.burton@arm.com \
--cc=changqing.li@windriver.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