summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2019-05-28 18:38:23 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-06-07 13:57:41 +0100
commit40233c62f8d657fdc08b5831f0577a9b81cda078 (patch)
treef0b4a954c5ed7f68441d7b85ba9a893cd811e684
parente6b1e54d85a740f9f44f7726109f6c4e3fdf31a6 (diff)
downloadpoky-40233c62f8d657fdc08b5831f0577a9b81cda078.tar.gz
dev-manual: Added check-upgrade-status blurb to upgrading recipes
The section "Upgrading Recipes" covers several ways of upgrading a recipe. I added some stuff in the introductory area that mentions the fact a user might want to check the upgrade status of a recipe first. (From yocto-docs rev: bd2fd8d0a91b64455c282ebf4974e40874274f46) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml18
1 files changed, 17 insertions, 1 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 9857e95a17..b2a13ed87b 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -4197,11 +4197,27 @@
4197 built by layer recipes. 4197 built by layer recipes.
4198 It is recommended to keep recipes up-to-date with upstream 4198 It is recommended to keep recipes up-to-date with upstream
4199 version releases. 4199 version releases.
4200 </para>
4201
4202 <para>
4203 While several methods exist that allow you upgrade a recipe,
4204 you might consider checking on the upgrade status of a recipe
4205 first.
4206 You can do so using the
4207 <filename>devtool check-upgrade-status</filename> command.
4208 See the
4209 "<ulink url='&YOCTO_DOCS_REF_URL;#devtool-checking-on-the-upgrade-status-of-a-recipe'>Checking on the Upgrade Status of a Recipe</ulink>"
4210 section in the Yocto Project Reference Manual for more information.
4211 </para>
4212
4213 <para>
4214 The remainder of this section describes three ways you can
4215 upgrade a recipe.
4200 You can use the Automated Upgrade Helper (AUH) to set up 4216 You can use the Automated Upgrade Helper (AUH) to set up
4201 automatic version upgrades. 4217 automatic version upgrades.
4202 Alternatively, you can use <filename>devtool upgrade</filename> 4218 Alternatively, you can use <filename>devtool upgrade</filename>
4203 to set up semi-automatic version upgrades. 4219 to set up semi-automatic version upgrades.
4204 Finally, you can even manually upgrade a recipe by editing the 4220 Finally, you can manually upgrade a recipe by editing the
4205 recipe itself. 4221 recipe itself.
4206 </para> 4222 </para>
4207 4223