diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-10-03 05:56:26 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-10-08 16:30:14 +0100 |
commit | b5ad5ba24b61b8b4f1e425a8357d18e5a02a06c9 (patch) | |
tree | ec22eb806fe3b201425487ac8ad467a82cfb7d6b /documentation/ref-manual/ref-classes.xml | |
parent | 7754bd215bc03493a1bf24779233cf285b3e6e44 (diff) | |
download | ast2050-yocto-poky-b5ad5ba24b61b8b4f1e425a8357d18e5a02a06c9.zip ast2050-yocto-poky-b5ad5ba24b61b8b4f1e425a8357d18e5a02a06c9.tar.gz |
ref-manual: Fixed cross-reference to runtime package management
A cross-reference section to the section in the dev-manual on
runtime package management needed updating. The patch from Trevor
broke the link.
(From yocto-docs rev: ad33880f09569e886dcf3dbb7f4cc9058ddecba5)
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/ref-classes.xml')
-rw-r--r-- | documentation/ref-manual/ref-classes.xml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index 2743059..e394122 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -341,9 +341,9 @@ on the development host that can be used by Smart, you can install packages from the feed while you are running the image on the target (i.e. runtime installation of packages). - For information on how to set up this repository, see the - "<ulink url='&YOCTO_DOCS_DEV_URL;#setting-up-runtime-package-management'>Setting Up Runtime Package Management</ulink>" - in the Yocto Project Development Manual. + For more information, see the + "<ulink url='&YOCTO_DOCS_DEV_URL;#runtime-package-management'>Runtime Package Management</ulink>" + section in the Yocto Project Development Manual. </para> <para> @@ -799,15 +799,15 @@ </para></listitem> <listitem><para><emphasis><filename>version-going-backwards:</filename></emphasis> If Build History is enabled, reports when a package - being written out has a lower version than the previously + being written out has a lower version than the previously written package under the same name. If you are placing output packages into a feed and - upgrading packages on a target system using that feed, the - version of a package going backwards can result in the target - system not correctly upgrading to the "new" version of the - package. + upgrading packages on a target system using that feed, the + version of a package going backwards can result in the target + system not correctly upgrading to the "new" version of the + package. <note> - If you are not using runtime package management on your + If you are not using runtime package management on your target system, then you do not need to worry about this situation. </note> |