diff options
author | Scott Rifenbark <srifenbark@gmail.com> | 2019-05-28 18:38:23 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-06-18 11:30:38 +0100 |
commit | 45115e603f5fdd660a76ec2632205f6d6df082ee (patch) | |
tree | b8b302f50c340b295e96018a4525c0cda86e341e | |
parent | cca5eb8ec3f6ffb54b1085b9b1f8623bc9e6a6bc (diff) | |
download | poky-45115e603f5fdd660a76ec2632205f6d6df082ee.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: 6747335d429b58251642c6b82d7725b0fe3e686e)
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.xml | 18 |
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 7476fbea67..316d0f5fb8 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml | |||
@@ -4196,11 +4196,27 @@ | |||
4196 | built by layer recipes. | 4196 | built by layer recipes. |
4197 | It is recommended to keep recipes up-to-date with upstream | 4197 | It is recommended to keep recipes up-to-date with upstream |
4198 | version releases. | 4198 | version releases. |
4199 | </para> | ||
4200 | |||
4201 | <para> | ||
4202 | While several methods exist that allow you upgrade a recipe, | ||
4203 | you might consider checking on the upgrade status of a recipe | ||
4204 | first. | ||
4205 | You can do so using the | ||
4206 | <filename>devtool check-upgrade-status</filename> command. | ||
4207 | See the | ||
4208 | "<ulink url='&YOCTO_DOCS_REF_URL;#devtool-checking-on-the-upgrade-status-of-a-recipe'>Checking on the Upgrade Status of a Recipe</ulink>" | ||
4209 | section in the Yocto Project Reference Manual for more information. | ||
4210 | </para> | ||
4211 | |||
4212 | <para> | ||
4213 | The remainder of this section describes three ways you can | ||
4214 | upgrade a recipe. | ||
4199 | You can use the Automated Upgrade Helper (AUH) to set up | 4215 | You can use the Automated Upgrade Helper (AUH) to set up |
4200 | automatic version upgrades. | 4216 | automatic version upgrades. |
4201 | Alternatively, you can use <filename>devtool upgrade</filename> | 4217 | Alternatively, you can use <filename>devtool upgrade</filename> |
4202 | to set up semi-automatic version upgrades. | 4218 | to set up semi-automatic version upgrades. |
4203 | Finally, you can even manually upgrade a recipe by editing the | 4219 | Finally, you can manually upgrade a recipe by editing the |
4204 | recipe itself. | 4220 | recipe itself. |
4205 | </para> | 4221 | </para> |
4206 | 4222 | ||