public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Subject: Re: [OE-core] [PATCH V2] appstream: upgrade from 1.0.6 to 1.1.2
Date: Fri, 13 Mar 2026 10:30:31 +0800	[thread overview]
Message-ID: <34e5b5a4-693d-4a31-8471-1a5495918593@windriver.com> (raw)
In-Reply-To: <189BA872138654D8.2412760@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 2419 bytes --]


On 3/11/26 10:27, Changqing Li via lists.openembedded.org wrote:
>
>
> On 3/10/26 19:44, Ross Burton wrote:
>> CAUTION: This email comes from a non Wind River email account!
>> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>
>> 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.
>
> Hi, Ross
>
> Indeed, very few packages offer this PACKAGECONFIG,but both oe-core 
> and meta-networking have one.
>
> I checked several recipes that inherit the class but not provide the 
> PACKAGECONFIG,
>
> all the recipes don't provide option to disable bash-completion. I 
> think this is why they don't provide PACKAGECONFIG.
>
Here I means that the recipes's upstream don't provide an option to 
disable bash-completion, eg:  apt, it will compiled with bash-completion 
by default,  there is no option

to enable/disable bash-completion.  So they don't need a PACKAGECONFIG. 
But appstream provdes option to enable/disable bash-completion. so I add 
one allow user to

disable it.

//Changqing

> upstream appstream provides the option to disable bash-completion, I 
> think we should keep the upstream option.
>
> Regards
>
> Changqing
>
>> Ross
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#232832):https://lists.openembedded.org/g/openembedded-core/message/232832
> Mute This Topic:https://lists.openembedded.org/mt/117989519/3616873
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [changqing.li@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

[-- Attachment #2: Type: text/html, Size: 5223 bytes --]

  parent reply	other threads:[~2026-03-13  2:30 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         ` [OE-core] " Ross Burton
2026-03-11  2:27           ` Changqing Li
     [not found]           ` <189BA872138654D8.2412760@lists.openembedded.org>
2026-03-13  2:30             ` Changqing Li [this message]
     [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=34e5b5a4-693d-4a31-8471-1a5495918593@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=Ross.Burton@arm.com \
    --cc=mathieu.dubois-briand@bootlin.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