Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Joshua Watt" <JPEWhacker@gmail.com>
To: docs@lists.yoctoproject.org
Cc: Joshua Watt <Joshua.Watt@garmin.com>
Subject: [docs][PATCH] dev-manual: Clarify that virtual providers do not apply to runtime dependencies
Date: Mon, 31 Aug 2020 12:20:57 -0500	[thread overview]
Message-ID: <20200831172057.34682-1-JPEWhacker@gmail.com> (raw)

From: Joshua Watt <Joshua.Watt@garmin.com>

Clarifies that virtual providers are only used for build time
dependencies specified with PROVIDES and DEPENDS, and do not apply to
runtime dependencies specified with RPROVIDES and RDEPENDS.

Signed-off-by: Joshua Watt <Joshua.Watt@garmin.com>
---
 documentation/dev-manual/dev-manual-common-tasks.xml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 1f24c7343..479ca4f20 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -3214,6 +3214,14 @@
                         </para></listitem>
                 </itemizedlist>
             </para>
+            <note>
+                Virtual providers only apply to build time dependencies with
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-PROVIDES'><filename>PROVIDES</filename></ulink>
+                and <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink>.
+                They do not apply to runtime dependencies specified with
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-RPROVIDES'><filename>RPROVIDES</filename></ulink> and
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-RDEPENDS'><filename>RDEPENDS</filename></ulink>.
+            </note>
         </section>
 
         <section id='properly-versioning-pre-release-recipes'>
-- 
2.28.0


                 reply	other threads:[~2020-08-31 17:21 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=20200831172057.34682-1-JPEWhacker@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=Joshua.Watt@garmin.com \
    --cc=docs@lists.yoctoproject.org \
    /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