openembedded-core.git/meta/recipes-devtools/build-compare, branch fido Mirror of openembedded-core build-compare: update Rename-rpm-check.sh-to-pkg-diff.sh.patch 2015-02-21T22:04:26+00:00 Robert Yang liezhi.yang@windriver.com 2015-02-20T05:57:18+00:00 14990de8c7481c3aaf77174a7541d5bfb9a7411d The patch can't be applied by "git am -3" with newer version of git (such as 2.0.1), and can't be applied by "git am/apply" with any version, now fix it Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The patch can't be applied by "git am -3" with newer version of git
(such as 2.0.1), and can't be applied by "git am/apply" with any
version, now fix it

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
build-compare: Add the build-compare_git.bb recipe. 2015-02-14T22:26:11+00:00 Randy Witt randy.e.witt@linux.intel.com 2015-02-12T00:24:12+00:00 48387f0c0c4cccc8bc89afd121b7d8315475964a The description for build-compare describes it as "This package contains scripts to find out if the build result differs to a former build." More specifically this contains a script that will display differences between "packages." It works with rpms, tarballs and other various types of packages. The idea is that it will eventually be used in Yocto to check for differences between sstate so that we can check for build reproducibility. It will also be used once an updateable sdk is in place, so that packages that have different hashes but are not different in contents, don't get updated. It could also be used in the same manner when updating packages from a package feed. [Yocto #6992] Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
The description for build-compare describes it as "This package contains
scripts to find out if the build result differs to a former build." More
specifically this contains a script that will display differences between
"packages." It works with rpms, tarballs and other various types of
packages.

The idea is that it will eventually be used in Yocto to check for differences
between sstate so that we can check for build reproducibility. It will
also be used once an updateable sdk is in place, so that packages that
have different hashes but are not different in contents, don't get updated.
It could also be used in the same manner when updating packages from a
package feed.

[Yocto #6992]

Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>