diff options
author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-07-14 09:04:25 +1200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-07-20 10:24:53 +0100 |
commit | fa550fcb9333d59b28fc0e4aebde888831410f5c (patch) | |
tree | e8b3b60565cd24bf09ccbe40379f9276af201051 /meta-skeleton | |
parent | 92eb42c347af919cd9f8739515fdf806c12b5ba8 (diff) | |
download | openembedded-core-fa550fcb9333d59b28fc0e4aebde888831410f5c.tar.gz openembedded-core-fa550fcb9333d59b28fc0e4aebde888831410f5c.tar.bz2 openembedded-core-fa550fcb9333d59b28fc0e4aebde888831410f5c.zip |
devtool: add finish subcommand
Add a subcommand which will "finish" the work on a recipe. This is
effectively the same as update-recipe followed by reset, except that the
destination layer is required and it will do the right thing depending
on the situation - if the recipe file itself is in the workspace (e.g.
as a result of devtool add), the recipe file and any associated files
will be moved to the destination layer; or if the destination layer is
the one containing the original recipe, the recipe will be overwritten;
otherwise a bbappend will be created to apply the changes. In all cases
the layer path can be loosely specified - it could be a layer name, or
a partial path into a recipe. In the case of upgrades, devtool finish
will also take care of deleting the old recipe.
This avoids the user having to figure out the correct actions when
they're done - they just do "devtool finish recipename layername" and
it saves their work and then removes the recipe from the workspace.
Addresses [YOCTO #8594].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta-skeleton')
0 files changed, 0 insertions, 0 deletions