All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose Quaresma <quaresma.jose@gmail.com>
To: Mikko Rapeli <mikko.rapeli@linaro.org>
Cc: meta-arm@lists.yoctoproject.org, ricardo@foundries.io,
	 Jose Quaresma <jose.quaresma@foundries.io>
Subject: Re: [meta-arm][PATCH 1/3] optee-ftpm/optee-os: add missing space in EXTRA_OEMAKE
Date: Thu, 27 Oct 2022 09:57:29 +0100	[thread overview]
Message-ID: <CANPvuRm=7D18721JuW6s-nAgdZbQEObehdQTKPfPSPJvxi_iXQ@mail.gmail.com> (raw)
In-Reply-To: <Y1oixbW4wq5PILX3@nuoska>

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

Hi Mikko,

Mikko Rapeli <mikko.rapeli@linaro.org> escreveu no dia quinta, 27/10/2022
à(s) 07:18:

> Hi,
>
> On Wed, Oct 26, 2022 at 02:18:52PM +0000, Jose Quaresma wrote:
> > When append to variable a space is required at the beginning.
> >
> > Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
> > ---
> >  meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
> b/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
> > index acea7502..40423615 100644
> > --- a/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
> > +++ b/meta-arm/recipes-security/optee-ftpm/optee-os_%.bbappend
> > @@ -7,7 +7,8 @@ DEPENDS:append = "\
> >                   '' , \
> >                   d)}"
> >
> > -EXTRA_OEMAKE:append = "${@bb.utils.contains('MACHINE_FEATURES', \
> > +EXTRA_OEMAKE:append = "\
>
> There is no need to use :append here. += will do and will add the
> space.


Right, I can use the += but in this case I follow this pattern to make the
change consistent
with what already existed in the file. I can change it, let's see the
maintainer's opinion.


>
> Using :append everywhere without machine or distro qualifiers is
> an annoying antipattern which intermediate layers should not use.
>
> Higher level product specific layers can't easily change the variables
> which have been amended with :append.
>

This will always be tricky to do, a lot due to the freedom of bitbake
syntax.
With :append usage we need to use the :remove because this needs to be done
at the end of the parsing.
While with += you can assign a new value for the variable during parsing
but you will lose all the others that had already possible been added with
+=

Great to talk with you again about bitbake stuff ;)

Jose


> Cheers,
>
> -Mikko
>


-- 
Best regards,

José Quaresma

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

  reply	other threads:[~2022-10-27  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 14:18 [meta-arm][PATCH 1/3] optee-ftpm/optee-os: add missing space in EXTRA_OEMAKE Jose Quaresma
2022-10-26 14:18 ` [meta-arm][PATCH 2/3] optee-ftpm/optee-os: rewite in a way to be less error prone Jose Quaresma
2022-10-27  6:19   ` Mikko Rapeli
2022-10-27  9:01     ` Jose Quaresma
2022-10-27 14:03   ` Jon Mason
2022-10-27 14:26     ` Jose Quaresma
2022-10-26 14:18 ` [meta-arm][PATCH 3/3] optee-os-ts: avoid using escape chars in EXTRA_OEMAKE Jose Quaresma
2022-10-27  6:20   ` Mikko Rapeli
2022-10-27 14:06     ` Jon Mason
2022-10-27  6:18 ` [meta-arm][PATCH 1/3] optee-ftpm/optee-os: add missing space " Mikko Rapeli
2022-10-27  8:57   ` Jose Quaresma [this message]
2022-10-27 21:38 ` [PATCH " Jon Mason

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='CANPvuRm=7D18721JuW6s-nAgdZbQEObehdQTKPfPSPJvxi_iXQ@mail.gmail.com' \
    --to=quaresma.jose@gmail.com \
    --cc=jose.quaresma@foundries.io \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=mikko.rapeli@linaro.org \
    --cc=ricardo@foundries.io \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.