public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [yocto-docs PATCH 13/14] ref-manual/variables: document the PREFERRED_RPROVIDER variable
Date: Tue, 17 Dec 2024 15:43:45 +0100	[thread overview]
Message-ID: <7be52ac3-ae7b-40ae-9bc2-69aa0b7f5d5e@cherry.de> (raw)
In-Reply-To: <20241217-release-note-5-2-updates-v1-13-b189493b1b09@bootlin.com>

Hi Antonin,

On 12/17/24 10:27 AM, Antonin Godard via lists.yoctoproject.org wrote:
> This variable is similar to the PREFERRED_PROVIDER variable but it
> denotes a runtime provider specifically.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/variables.rst | 19 +++++++++++++++++++
>   1 file changed, 19 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 50cd8948b35f381414837acc9b9e925dc5110779..e0b87c0e5ff8cf7bd2598cbbb184f9aada19d326 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -6711,6 +6711,25 @@ system and gives an overview of their function and contents.
>      :term:`PREFERRED_PROVIDERS`
>         See :term:`bitbake:PREFERRED_PROVIDERS` in the BitBake manual.
>   
> +   :term:`PREFERRED_RPROVIDER`
> +      The :term:`PREFERRED_RPROVIDER` variable works like the
> +      :term:`PREFERRED_PROVIDER` variable, but it denotes recipes that provide a
> +      *runtime* component. Runtime providers are declared by recipes that set
> +      the :term:`RPROVIDES` variable. For example::
> +
> +        PREFERRED_RPROVIDER_virtual-x-terminal-emulator = "rxvt-unicode"

Missing a whitespace for the alignment I believe (I believe we're 
three-whitespace aligned usually?). Ditto for the other code blocks below.

> +
> +      This statement sets the runtime provider for the X terminal emulator to
> +      ``rxvt-unicode``. The ``rxvt-unicode`` recipe is a runtime provider of
> +      this component because it contains the following :term:`RPROVIDES`
> +      definition::
> +
> +        RPROVIDES:${PN} = "virtual-x-terminal-emulator"
> +

We have to be very careful with the word recipe here. Above, it's the 
``rxvt-unicode`` package that is a runtime provider of 
virtual-x-terminal-emulator, because of the :${PN} override.

I assume PREFERRED_RPROVIDER_virtual-x-terminal-emulator should also 
contain the name of the package and not the recipe? That I am not 
entirely sure of though, haven't looked into the implementation of it.

Cheers,
Quentin


  reply	other threads:[~2024-12-17 14:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  9:26 [yocto-docs PATCH 00/14] Updates from recent core changes Antonin Godard
2024-12-17  9:27 ` [yocto-docs PATCH 01/14] ref-manual/variables: document the KERNEL_CONSOLE variable Antonin Godard
2024-12-17 10:05   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 02/14] ref-manual/classes: drop the migrate_localcount class Antonin Godard
2024-12-17 10:14   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 03/14] ref-manual/variables: document the FIRMWARE_COMPRESSION variable Antonin Godard
2024-12-17 10:28   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 04/14] ref-manual/variables: add missing entries to SDK_ARCHIVE_TYPE Antonin Godard
2024-12-17 10:34   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 05/14] ref-manual/variables: document the WIC_SECTOR_SIZE variable Antonin Godard
2024-12-17 10:37   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 06/14] ref-manual/variable: remove obsolete SETUPTOOLS_INSTALL_ARGS Antonin Godard
2024-12-17 10:39   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 07/14] ref-manual/classes: document the cython class Antonin Godard
2024-12-17 10:48   ` [docs] " Quentin Schulz
2024-12-20  9:06     ` Antonin Godard
2024-12-17  9:27 ` [yocto-docs PATCH 08/14] Remove debug-tweaks references Antonin Godard
2024-12-17  9:27 ` [yocto-docs PATCH 09/14] Drop support for BB_DANGLINGAPPENDS_WARNONLY Antonin Godard
2024-12-17 14:08   ` [docs] " Quentin Schulz
2024-12-20  9:17     ` Antonin Godard
2024-12-17  9:27 ` [yocto-docs PATCH 10/14] ref-manual/variables: document the CHECKLAYER_REQUIRED_TESTS variable Antonin Godard
2024-12-17 14:14   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 11/14] ref-manual/classes: document the yocto-check-layer class Antonin Godard
2024-12-17 14:15   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 12/14] ref-manual/variables: document the CARGO_INSTALL_LIBRARIES variable Antonin Godard
2024-12-17 14:32   ` [docs] " Quentin Schulz
2024-12-17  9:27 ` [yocto-docs PATCH 13/14] ref-manual/variables: document the PREFERRED_RPROVIDER variable Antonin Godard
2024-12-17 14:43   ` Quentin Schulz [this message]
2024-12-20 10:31     ` [docs] " Antonin Godard
2024-12-17  9:27 ` [yocto-docs PATCH 14/14] migration-guides: update the release notes for 5.2 Antonin Godard

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=7be52ac3-ae7b-40ae-9bc2-69aa0b7f5d5e@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=thomas.petazzoni@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