aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/python/python-async_0.6.2.bb
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2015-08-28 16:51:26 +0100
committerPaul Eggleton <paul.eggleton@linux.intel.com>2015-09-08 14:25:58 +0100
commit6b6d4faae6721915597cd9da2a2d1b1b69fa8c11 (patch)
tree7a46b3607e3807543239850de4ed8bef7b0bfe57 /meta/recipes-devtools/python/python-async_0.6.2.bb
parente2372e183b9a2f8c2e53d0a57f5a1211ef5a5331 (diff)
downloadopenembedded-core-contrib-paule/packagefeed-stability.tar.gz
WIP: classes/packagefeed-stability: add class to help reduce package feed churnpaule/packagefeed-stability
When a dependency causes a recipe to effectively be rebuilt, its output may in fact not change; but new packages (with an increased PR value, if using the PR server) will be generated nonetheless. There's no practical way for us to predict whether or not this is going to be the case based solely on the inputs, but we can compare the package output and see if that is materially different and based upon that decide to replace the old package with the new one. This class effectively intercepts packages as they are written out by do_package_write_*, causing them to be written into a different directory where we can compare them to whatever older packages might be in the "real" package feed directory, and avoid copying the new package to the feed if it has not materially changed. We use build-compare to do the package comparison. (NOTE: this is still a work in progress and there are no doubt unresolved issues.) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Diffstat (limited to 'meta/recipes-devtools/python/python-async_0.6.2.bb')
0 files changed, 0 insertions, 0 deletions