public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: michael.opdenacker@bootlin.com
Cc: bitbake-devel@lists.openembedded.org, docs@lists.yoctoproject.org
Subject: Re: [bitbake-devel] [PATCH] bitbake-user-manual: explicit variables taking a colon separated list
Date: Tue, 20 Jun 2023 09:52:30 +0200	[thread overview]
Message-ID: <20230620095230.3847067a@booty> (raw)
In-Reply-To: <20230619160614.909233-1-michael.opdenacker@bootlin.com>

Hi Mike,

On Mon, 19 Jun 2023 18:06:14 +0200
"Michael Opdenacker via lists.openembedded.org"
<michael.opdenacker=bootlin.com@lists.openembedded.org> wrote:

> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
> 
> [YOCTO #15128]
> 
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> ---
>  .../bitbake-user-manual-ref-variables.rst        | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> index 01d4f8d1..ee5d7ba8 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> @@ -920,9 +920,9 @@ overview of their function and contents.
>        section.
>  
>     :term:`BBPATH`
> -      Used by BitBake to locate class (``.bbclass``) and configuration
> -      (``.conf``) files. This variable is analogous to the ``PATH``
> -      variable.
> +      A colon-separated list used by BitBake to locate class (``.bbclass``)
> +      and configuration (``.conf``) files. This variable is analogous to the
> +      ``PATH`` variable.
>  
>        If you run BitBake from a directory outside of the build directory,
>        you must be sure to set :term:`BBPATH` to point to the build directory.
> @@ -1165,8 +1165,8 @@ overview of their function and contents.
>        order.
>  
>     :term:`OVERRIDES`
> -      BitBake uses :term:`OVERRIDES` to control what variables are overridden
> -      after BitBake parses recipes and configuration files.
> +      A colon-separated list that BitBake uses to control what variables are
> +      overridden after BitBake parses recipes and configuration files.
>  
>        Following is a simple example that uses an overrides list based on
>        machine architectures: OVERRIDES = "arm:x86:mips:powerpc" You can
> @@ -1225,9 +1225,9 @@ overview of their function and contents.
>           PREFERRED_PROVIDER_virtual/libgl ?= "mesa"
>  
>     :term:`PREFERRED_PROVIDERS`
> -      Determines which recipe should be given preference for cases where
> -      multiple recipes provide the same item. Functionally,
> -      :term:`PREFERRED_PROVIDERS` is identical to
> +      A colon-separated list to determine which recipe should be given
> +      preference for cases where multiple recipes provide the same item.
> +      Functionally, :term:`PREFERRED_PROVIDERS` is identical to
>        :term:`PREFERRED_PROVIDER`. However, the :term:`PREFERRED_PROVIDERS` variable
>        lets you define preferences for multiple situations using the following
>        form::

If I read the docs correctly, PREFERRED_PROVIDERS is not a
colon-separated list but rather a space-separated list [of
colon-separated pairs].

Otherwise looks good, and useful -- thanks!

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-06-20  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 16:06 [PATCH] bitbake-user-manual: explicit variables taking a colon separated list michael.opdenacker
2023-06-20  7:52 ` Luca Ceresoli [this message]
2023-06-20 17:03   ` [bitbake-devel] " Michael Opdenacker

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=20230620095230.3847067a@booty \
    --to=luca.ceresoli@bootlin.com \
    --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