Re: [bitbake-devel] [PATCH] doc/bitbake-user-manual-ref-variables: document PREFERRED_RPROVIDER

Hi Yann,

On 8/24/26 12:12 PM, Yann Dirson via lists.openembedded.org wrote:
> [You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> Signed-off-by: Yann Dirson <[email protected]>
> ---
>   .../bitbake-user-manual-ref-variables.rst                | 9 +++++++++
>   1 file changed, 9 insertions(+)
> 
> 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 5395ce5e3..2756fc0c4 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
> @@ -1558,6 +1558,15 @@ overview of their function and contents.
>            PREFERRED_PROVIDER_xxx = "yyy"
>            PREFERRED_PROVIDER_aaa = "bbb"
> 
> +   :term:`PREFERRED_RPROVIDER` Determines which recipe should be given

Please be consistent with the rest of the file. 
:term:`PREFERRED_RPROVIDER` should be on its own on the first line.

> +      preference when multiple packages rprovide the same item. Beware

rprovide is not an English term so all readers won't necessarily know 
what this means. I can suggest:

"""
Determines which *recipe* generating a package runtime-providing 
(:term:`RPROVIDES`) the same item as other packages should be given 
preference. Some examples::
[...]


"""

> +      this should contain the name of the *recipe* producing the
> +      package that rprovides the item, not that of the package. Some
> +      examples::
> +
> +         PREFERRED_RPROVIDER_initd-functions ?= "initscripts"
> +         PREFERRED_RPROVIDER_virtual-libegl-icd ?= "mesa"

Are you sure this is still valid? I don't see an RPROVIDES for 
virtual-libegl-icd so maybe this is not doing anything?

Cheers,
Quentin