All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Kiernan <alex.kiernan@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org,
	Otavio Salvador <otavio.salvador@ossystems.com.br>,
	Alex Kiernan <alexk@zuma.ai>
Subject: Re: [bitbake-devel] [PATCH] data_smart: Pass flags through variable rename
Date: Thu, 9 Jun 2022 11:33:03 +0100	[thread overview]
Message-ID: <CAO5Uq5QPsf8Lj8qYCibMD-m+0R7Na_ipU4WehYL3Oqu_rk4dRA@mail.gmail.com> (raw)
In-Reply-To: <5e781972643ed99e2948ac5a908222a190678475.camel@linuxfoundation.org>

Not that I've found, but I'd really like to use it... I've a layer for
s6-rc (https://skarnet.org/software/s6-rc/) and defining the
configuration using this syntax works really well:

S6_RC_SERVICE_${BPN} ?= "longrun"
S6_RC_SERVICE_${BPN}[producer-for] ?= "${BPN}-log"
S6_RC_SERVICE_${BPN}-log ?= "longrun"
S6_RC_SERVICE_${BPN}-log[consumer-for] ?= "${BPN}"
S6_RC_SERVICE_${BPN}-log[notification-fd] ?= "3"
S6_RC_SERVICE_${BPN}-log[pipeline-name] ?= "${BPN}-pipeline"
S6_RC_SERVICE_${BPN}-log[run] ?= "${@ d.getVar('s6_rc_log') }"

Is the kind of thing I'd like to work.

On Thu, Jun 9, 2022 at 10:58 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Thu, 2022-06-09 at 08:06 +0100, Alex Kiernan wrote:
> > During variable expansion, the flags are not passed through but are
> > discarded which makes constructs such as:
> >
> >   ALTERNATIVE_TARGET:${PN}-foo[name] = "value"
>
> This is a tricky one. I don't think we've ever supported overrides and
> flags combined? Is this in use in metadata?
>
> Cheers,
>
> Richard



-- 
Alex Kiernan


  reply	other threads:[~2022-06-09 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  7:06 [PATCH] data_smart: Pass flags through variable rename Alex Kiernan
2022-06-09  9:58 ` [bitbake-devel] " Richard Purdie
2022-06-09 10:33   ` Alex Kiernan [this message]
     [not found]   ` <16F6ED45D7C68CA7.32696@lists.openembedded.org>
2022-06-16 12:27     ` Alex Kiernan
2022-06-27 11:10       ` Richard Purdie
2022-06-28 11:13         ` Alex Kiernan

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=CAO5Uq5QPsf8Lj8qYCibMD-m+0R7Na_ipU4WehYL3Oqu_rk4dRA@mail.gmail.com \
    --to=alex.kiernan@gmail.com \
    --cc=alexk@zuma.ai \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --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 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.