linux/poky.git/meta/recipes-devtools/build-compare, branch 2.7_M2

oe-core: take UPSTREAM_CHECK_COMMITS into use where possible

2017-11-30T10:49:22+00:00

This greatly reduces the amount of recipes for which upstream version check fails: from about 30 to about 8. (From OE-Core rev: bb9066670a6096aa4134bebc84132b4eb3964b6d) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

selftest: fix distrodata.py to use per-recipe UPSTREAM_VERSION_UNKNOWN setting

2017-08-15T23:03:13+00:00

... instead of a global exception list which was problematic. [YOCTO #11896] (From OE-Core rev: 89dfede4ca795ba085f1ee7290c6dede573c11db) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

build-compare: add date to PV

2017-03-17T16:53:05+00:00

We want PV values to be easily ordered, so use the latest entry in build-compare.changes which will also match the date of SRCREV. (From OE-Core rev: c796cd4ac39e704e0795385c9b4ec9a2d73459b5) Signed-off-by: Joe Slater Signed-off-by: Richard Purdie

meta: do not append to BBCLASSEXTEND

2017-03-10T14:50:11+00:00

Replace some "+=/=+" with "=" when setting BBCLASSEXTEND, they are redundant and inconsistent with the same setting in other recipes. (From OE-Core rev: 09266d6c91acd8ba4df6e8242aa44d9ba41e9cee) Signed-off-by: Ming Liu Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

build-compare: derive PV from SRCPV

2017-01-23T12:05:22+00:00

Currently, PV is "git" and contains no version information. (From OE-Core rev: e1fe3f8a601ba289a2e9963ef3f1309e431704eb) Signed-off-by: Joe Slater Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

build-compare: improve deb and ipk checking

2016-07-26T07:56:28+00:00

* The deb and ipk's depends version string is like: Depends: libc6 (>= 2.24) Update trim_release_old and trim_release_new to match the bracket in the end ")". * The deb's data tarball now is .tar.xz, and ipk's is .tar.gz. * Update adjust_controlfile() to make ituse trim_release_old and trim_release_new. (From OE-Core rev: c92152e521a9f96a741eccd4a4bf5ddfbd59a7ae) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

build-compare: fix checking for named pipe and others

2016-07-26T07:56:28+00:00

* Fixed checking for named pipe * Return at once when archives are the same * Fix for type "directory" (From OE-Core rev: e3245747342860da44fcbb49ac68b8b33e5b43a3) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

build-compare: make pkg-diff.sh 75% faster

2016-07-26T07:56:28+00:00

The rpm tool is a heavy process, pkg-diff.sh ran 16 (or 17 for kernel) "rpm -qp" times when the pkgs are identical, now we only run "rpm -qp --qf " twice (one is for old pkg, and one is for new), save the results to spec_old and spec_new, then use sed command to get what we need later, this can make it 75% faster when the pkgs are identical. Here is the rough data on my host Ubuntu 14.04.4, 32 cores CPU and 128G mem: * When the pkgs are identical: - Before the patch: 1s - After the patch: 0.26s I compare the whole spec firstly, and return 0 if they are the same, or go on checking one by one if not, without this, it would be 0.46s, the gain is great when there are lot of packages, usually, we have more than 10,000 rpms to compare. * When the pkgs are different: That depends on where is the different, if the different is at the comparing rpmtags stage: - Before the patch: 0.26s - After the patch: 0.29s Increased 0.03s, but if the different is happend later than comparing rpmtags, it will save time. (From OE-Core rev: 71eee4adbcda1d9e75cbce58045d03ea12432431) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

build-compare: remove space at head

2016-07-26T07:56:28+00:00

The command like: rpm -qp --nodigest --nosignature --qf ' [%{REQUIRENAME}\n]\n' ^^space The space will be printed, and will impact the check result, so remove it. (From OE-Core rev: 79c574979f64f2dbe8ca05774446de21a53b3a87) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

build-compare: drop PATCHTOOL setting

2015-10-19T16:57:57+00:00

We don't need PATCHTOOL to be set to git in this recipe, and setting it that way requires that the running user has git user & email configured, which on a build server it might well not be. (From OE-Core rev: ae8dcdc3c8e090fe392de86dc59135a38f06e9ca) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie