public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	"alex.kanavin@gmail.com" <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] appstream: upgrade from 1.0.6 to 1.1.2
Date: Wed, 25 Feb 2026 11:28:05 +0800	[thread overview]
Message-ID: <cb25c981-4623-4c95-87f5-c6677414d4be@windriver.com> (raw)
In-Reply-To: <DB5PR02MB102138725558AB810833F8DFCEF74A@DB5PR02MB10213.eurprd02.prod.outlook.com>


On 2/24/26 23:44, Peter Kjellerstedt 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.
>
>> -----Original Message-----
>> From: openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org> On Behalf Of Alexander Kanavin via lists.openembedded.org
>> Sent: den 24 februari 2026 10:59
>> To: changqing.li@windriver.com
>> Cc: openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH 2/2] appstream: upgrade from 1.0.6 to 1.1.2
>>
>> On Tue, 24 Feb 2026 at 02:42, Changqing Li via lists.openembedded.org <changqing.li=windriver.com@lists.openembedded.org> wrote:
>>
>>> +PACKAGECONFIG:class-target += "bash-completion"
> That should be:
>
> PACKAGECONFIG:append:class-target = " bash-completion"
>
> or it will replace the PACKAGECONFIG for target rather than
> add to it.
>
>>>   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,bash-completion"
> Remove the dependency on bash-completion (see below).
>
>> bash-completion can perhaps stay disabled for both native and target?
>>
>> Alex
> No, better is to instead inherit the bash-completion bbclass so the
> file(s) are packaged separately, and installed automatically when
> the bash-completion-pkgs feature is enabled.

Thanks  Peter and Alex.  I will send a V2 according to the comments.

//Changqing

>
> //Peter
>


  reply	other threads:[~2026-02-25  3:28 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 [this message]
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
     [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=cb25c981-4623-4c95-87f5-c6677414d4be@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=alex.kanavin@gmail.com \
    --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