summaryrefslogtreecommitdiff
path: root/oe-init-build-env
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2016-02-19 22:38:58 +1300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-02-21 09:32:00 +0000
commit41fed83060f0041e14e455d1446397bda277d953 (patch)
treeef1690aee92354127f787d728bdc91c881d42e29 /oe-init-build-env
parenta16a0c9334b785e2df896266c8911a2c7a1806b8 (diff)
downloadopenembedded-core-41fed83060f0041e14e455d1446397bda277d953.tar.gz
openembedded-core-41fed83060f0041e14e455d1446397bda277d953.tar.bz2
openembedded-core-41fed83060f0041e14e455d1446397bda277d953.zip
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. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'oe-init-build-env')
0 files changed, 0 insertions, 0 deletions