All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ola x Nilsson" <ola.x.nilsson@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH 2/2] bin/bitbake-getvar: Add a new command to query a variable value (with history)
Date: Fri, 23 Apr 2021 20:03:10 +0200	[thread overview]
Message-ID: <jwqv98cri8x.fsf@axis.com> (raw)
In-Reply-To: <20210416171126.1373752-2-richard.purdie@linuxfoundation.org>


On fri, apr 16 2021, Richard Purdie wrote:

> We've talked about having this for long enough. Add a command which queries a single
> variable value with history. This saves "bitbake -e | grep" and avoids the
> various pitfalls that has.
>
> It also provides a neat example of using tinfoil to make such a query.
>
> Parameters to limit the output to just the value, to limit to a variable flag
> and to not expand the output are provided.

I think this will be a very useful tool.  I have hacked (as in I really
don't want to show anyone the code) something similar together on top of
bitbake -e and I've found this commandline very useful

bitbake-getvar RECIPE VARIABLE [VARIABLE...]

so that I do not have to repeat the command when I want to examine more
than one variable.  Expanding with VARIABLE[FLAG] syntax would be nice.
Of course, if you want to examine several flags for a variable that will
mean a lot of extra typing.

I chose to add a -g flag for --global, as in no specific recipe so it is
kind of reverse of this command's options.

Just my 2 cents

/Ola

      parent reply	other threads:[~2021-04-23 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 17:11 [PATCH 1/2] tinfoil/data_smart: Allow variable history emit() to function remotely Richard Purdie
2021-04-16 17:11 ` [PATCH 2/2] bin/bitbake-getvar: Add a new command to query a variable value (with history) Richard Purdie
2021-04-19 21:36   ` [bitbake-devel] " Paul Eggleton
2021-04-20 15:12     ` Ross Burton
2021-04-20 15:29       ` Christopher Larson
2021-04-23 18:03   ` Ola x Nilsson [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=jwqv98cri8x.fsf@axis.com \
    --to=ola.x.nilsson@axis.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --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.