diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-04-01 15:18:09 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-04-04 15:20:16 +0100 |
commit | 583b6a45273e1c71ce39427b670612550612bc70 (patch) | |
tree | 37f2d87d7101e5447f94e31b9d28bc422a2e4733 /documentation | |
parent | 2741cd5e29f64a7ce59f008188da4dde6ec87f42 (diff) | |
download | ast2050-yocto-poky-583b6a45273e1c71ce39427b670612550612bc70.zip ast2050-yocto-poky-583b6a45273e1c71ce39427b670612550612bc70.tar.gz |
ref-manual: Edits to RDEPENDS variable.
The do_package_write task has been removed leaving only
do_package_write_* tasks. This variable description had an
example using that obsoleted name. I changed it to
do_package_write_ipk.
(From yocto-docs rev: ec1c33a867f539cd83d672845075f2437cd917ed)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/ref-manual/ref-variables.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 8fcf5fb..48f8965 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -5813,7 +5813,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" <filename>do_build</filename> task depends on the existence of a specific package. Consider this simple example for two recipes named "a" and - "b" that produce similarly named packages. + "b" that produce similarly named IPK packages. In this example, the <filename>RDEPENDS</filename> statement appears in the "a" recipe: <literallayout class='monospaced'> @@ -5821,13 +5821,13 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" </literallayout> Here, the dependency is such that the <filename>do_build</filename> task for recipe "a" depends - on the <filename>do_package_write</filename> task + on the <filename>do_package_write_ipk</filename> task of recipe "b". This means the package file for "b" must be available when the output for recipe "a" has been completely built. More importantly, package "a" will be marked as depending on package "b" in a manner that is understood by the - package manager in use (i.e. rpm, opkg, or dpkg). + package manager. </para> <para> |