public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jacob Kroon <jacob.kroon@gmail.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	richard.purdie@linuxfoundation.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] selftest/imagefeatures/overlayfs: Always append to DISTRO_FEATURES
Date: Mon, 16 May 2022 15:18:04 +0200	[thread overview]
Message-ID: <eafd8c17-02e4-9ff9-3e9b-df806f3dbaa4@gmail.com> (raw)
In-Reply-To: <e6c6fc91-5e14-3084-40e0-ac4e8be76c1b@theobroma-systems.com>

On 5/16/22 15:01, Quentin Schulz wrote:
> Hi Jacob,
> 
> On 5/16/22 14:52, Jacob Kroon wrote:
>> On 5/16/22 14:38, richard.purdie@linuxfoundation.org wrote:
>>> On Mon, 2022-05-16 at 13:43 +0200, Jacob Kroon wrote:
>>>> Hi Richard,
>>>>
>>>> On 5/16/22 13:28, Richard Purdie wrote:
>>>>> Using += unintentionally removes all over entries from 
>>>>> DISTRO_FEATURES and
>>>>
>>>> "over", you mean "other" ? If so, how is that possible ?
>>>
>>> I mean other, I'll fix the typo. It happens due to:
>>>
>>> meta-poky/conf/distro/poky.conf:DISTRO_FEATURES ?= 
>>> "${DISTRO_FEATURES_DEFAULT} ${POKY_DEFAULT_DISTRO_FEATURES}"
>>>
>>> which interacts badly with "+=" :(
>>>
>>> I'm not happy about the situation with variable interactions but still
>>> not entirely sure the best way to proceed.
>>>
>>
>> That is surprising to me. I tried this snippet in a Makefile:
>>
>> foo ?= bar1
>>
>>
>>
>> foo += bar2
>>
> 
> Same for Bitbake.
> 
> However:
> foo += bar2
> 
> foo ?= bar1
> 
> will return " bar2", while make returns "bar2" (note the missing leading 
> space).
> 
> The issue is where the ?= is located. If it is in a recipe, 
> configuration files need to use :append otherwise they will override ?= 
> (as configuration files are parsed before recipes).
> 

Right, I see. So the "+="-operator is behaving as expected, but in this 
case the order of the statements forces usage of the append-override :-/

Jacob


      reply	other threads:[~2022-05-16 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 11:28 [PATCH] selftest/imagefeatures/overlayfs: Always append to DISTRO_FEATURES Richard Purdie
2022-05-16 11:43 ` [OE-core] " Jacob Kroon
2022-05-16 12:38   ` richard.purdie
2022-05-16 12:52     ` Jacob Kroon
2022-05-16 12:54       ` richard.purdie
2022-05-16 13:01       ` Quentin Schulz
2022-05-16 13:18         ` Jacob Kroon [this message]

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=eafd8c17-02e4-9ff9-3e9b-df806f3dbaa4@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=richard.purdie@linuxfoundation.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