summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-03-28 11:30:31 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-04 14:13:40 +0100
commit9875a46a2d778a4e6538ef88470bff21bfc14f79 (patch)
treea58da7f5cb6ba416778641fb25d46f4fdd28d807 /documentation/ref-manual
parentbcc9239c13106b5bb89aec8084809d96d45d1625 (diff)
downloadpoky-9875a46a2d778a4e6538ef88470bff21bfc14f79.tar.gz
ref-manual: Edits to PACKAGES_DYNAMIC variable.
(From yocto-docs rev: 85726f6819d5c1fe1c0ad32c3bc663b1364f78c6) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r--documentation/ref-manual/ref-variables.xml10
1 files changed, 7 insertions, 3 deletions
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 8bf8aa4ec6..187741bf7e 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -2481,18 +2481,22 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
2481 does not actually satisfy the dependencies, it only states that 2481 does not actually satisfy the dependencies, it only states that
2482 they should be satisfied. 2482 they should be satisfied.
2483 For example, if a hard, runtime dependency 2483 For example, if a hard, runtime dependency
2484 (<filename>RDEPENDS</filename>) of another package is satisfied 2484 (<link linkend='var-RDEPENDS'><filename>RDEPENDS</filename></link>)
2485 of another package is satisfied
2485 at build time through the <filename>PACKAGES_DYNAMIC</filename> 2486 at build time through the <filename>PACKAGES_DYNAMIC</filename>
2486 variable, but a package with the module name is never actually 2487 variable, but a package with the module name is never actually
2487 produced, then the other package will be broken. 2488 produced, then the other package will be broken.
2488 Thus, if you attempt to include that package in an image, 2489 Thus, if you attempt to include that package in an image,
2489 you will get a dependency failure from the packaging system 2490 you will get a dependency failure from the packaging system
2490 during <filename>do_rootfs</filename>. 2491 during <filename>do_rootfs</filename>.
2492 </para>
2493 <para>
2491 Typically, if there is a chance that such a situation can 2494 Typically, if there is a chance that such a situation can
2492 occur and the package that is not created is valid 2495 occur and the package that is not created is valid
2493 without the dependency being satisfied, then you should use 2496 without the dependency being satisfied, then you should use
2494 <filename>RRECOMMENDS</filename> (a soft runtime dependency) 2497 <link linkend='var-RRECOMMENDS'><filename>RRECOMMENDS</filename></link>
2495 instead of <filename>RDEPENDS</filename>. 2498 (a soft runtime dependency) instead of
2499 <filename>RDEPENDS</filename>.
2496 </para> 2500 </para>
2497 2501
2498 <para> 2502 <para>