public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
	 bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org
Subject: Re: [bitbake-devel] [PATCH] doc: bitbake-user-manual: fix syntax in example and improve description
Date: Thu, 22 Jul 2021 23:14:42 +0100	[thread overview]
Message-ID: <a7519c3f91a397c4e4259be88c0ccd76c3b2f037.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210722171021.69225-1-michael.opdenacker@bootlin.com>

Hi Michael,

On Thu, 2021-07-22 at 19:10 +0200, Michael Opdenacker wrote:
> The previous syntax of the example was clearly incorrect
> The example and description were also ambiguous, one could think that
> it was "bitbake recipe" instead of "bitbake <recipename>"
> 
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> ---
>  doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
> index 20c330e6..01ac4d5e 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
> @@ -91,9 +91,10 @@ level changes:
>        Variables that are exported to the environment are preceded by the
>        string "export" in the command's output.
>  
> 
> 
> 
> --  For recipe changes, use the following::
> +-  To find changes to a given variable in a specific recipe, use the
> +   following::
>  
> 
> 
> 
> -      $ bitbake recipe -e \| grep VARIABLE="
> +      $ bitbake recipename -e | grep VARIABLENAME=\"
>  
> 
> 
> 
>     This command checks to see if the variable actually makes
>     it into a specific recipe.



I should probably highlight there is a new command, "bitbake-getvar":

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=7bbeddeee1992d8c8fb71ba2dd49b03d0ae1ce86

We probably want to document that.

Whilst I'm thinking about it, the override discussions on the architecture list
are going to have implications for documentation too.

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=75fad23fc06c008a03414a1fc288a8614c6af9ca

An example of my scripted conversion run against the manuals is included
in this commit:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/diff/documentation/ref-manual/variables.rst?h=rpurdie/overrides-convert&id=9ac22a64a4c0ac4640552e90674e6459f0fece9a



Cheers,

Richard



  reply	other threads:[~2021-07-22 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 17:10 [PATCH] doc: bitbake-user-manual: fix syntax in example and improve description Michael Opdenacker
2021-07-22 22:14 ` Richard Purdie [this message]
2021-07-23  8:35   ` [docs] [bitbake-devel] " Michael Opdenacker
2021-07-26 21:39     ` Richard Purdie
     [not found]   ` <16945E9217B4CF53.14473@lists.openembedded.org>
2021-07-26 15:44     ` Michael Opdenacker
2021-07-26 21:45       ` Richard Purdie

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=a7519c3f91a397c4e4259be88c0ccd76c3b2f037.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.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