Extend the tool in bug 6659 to add the ability to compare the output sstate packages to see if they have materially changed. Those that have not can be preserved in the manifest in order to reduce the amount an existing user needs to download in order to upgrade. (Note: if the manifest is also embedded within the SDK that will also need to be updated).
Module: openembedded-core.git Branch: master Commit: c201ab826046b30281341107b3e6a35204f5c9d8 URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=c201ab826046b30281341107b3e6a35204f5c9d8 Author: Qi.Chen@windriver.com <Qi.Chen@windriver.com> Date: Mon Sep 7 13:42:26 2015 +0100 oe-publish-sdk: add script Add a script to publish an extensible SDK that has previously been built to a specified destination. This published SDK is intended to be accessed by the devtool sdk-update command from an installed copy of the extensible SDK. e.g. oe-publish-sdk <ext-sdk> <destination> Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Does oe-publish-sdk actually do comparisons of the packages in order to determine if they should be published or not?
Sorry, I misunderstood it. Reopen this bug. //Qi
I'll look at the latest situation of devtool and see how to fit into that.
Please look into whether or not this feature is still relevant.
So I believe as of recently this is now handled in a different way through the sstate hash equivalency functionality, so marking as resolved.