From: michael.opdenacker@bootlin.com
To: bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org,
Michael Opdenacker <michael.opdenacker@bootlin.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: [PATCH] bitbake-user-manual: revert change about PREFERRED_PROVIDERS
Date: Tue, 20 Jun 2023 19:53:00 +0200 [thread overview]
Message-ID: <20230620175300.1132976-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Partially reverting https://git.openembedded.org/bitbake/commit/?id=d1779e2f7789e516efae434b3781c981d0ef4ded
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
---
.../bitbake-user-manual-ref-variables.rst | 6 +++---
1 file changed, 3 insertions(+), 3 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 ee5d7ba8..2032157f 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
@@ -1225,9 +1225,9 @@ overview of their function and contents.
PREFERRED_PROVIDER_virtual/libgl ?= "mesa"
:term:`PREFERRED_PROVIDERS`
- 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
+ Determines 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::
--
2.34.1
reply other threads:[~2023-06-20 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230620175300.1132976-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=luca.ceresoli@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