diff options
| author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-02-19 22:38:58 +1300 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-02-21 09:32:42 +0000 |
| commit | 2059a344b60837b83261a713eb8cbcd34657a73d (patch) | |
| tree | a4a1896bb57892f9a87282652852b146ed92c8fc /meta/recipes-extended | |
| parent | b95c72c4dcac97b00ad46cd6b0ff0a854a0e867f (diff) | |
| download | poky-2059a344b60837b83261a713eb8cbcd34657a73d.tar.gz | |
devtool: undeploy-target: support undeploying all recipes
If you want to put the target device back to exactly how it was before
devtool deploy-target started poking things into it, then it would make
things easier if you didn't have to figure out which recipes were
deployed. Now that we have the list stored on the target we can
determine this reliably, so add a -a/--all option to undeploy-target to
undeploy everything that has been deployed.
One of the side-effects of this is that the dry-run functionality for
undeploy-target had to be reimplemented to actually run the script on
the target, since we have no way of knowing what's been deployed from
the host side. We don't need to do the same for deploy-target though
since we know exactly which files will be deployed without referring to
the target.
(From OE-Core rev: 41fed83060f0041e14e455d1446397bda277d953)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended')
0 files changed, 0 insertions, 0 deletions