linux/poky.git/meta/recipes-devtools/rpm/rpmresolve, branch pyro-next

rpmresolve: remove the recipe

2017-03-14T14:42:16+00:00

The source code is incompatible with rpm4 API - let's use rpm binary itself for now. (From OE-Core rev: 127112fa05c7102dacda4173adf380c557bacecb) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

rpmresolve.c: Fix unfreed pointers that keep DB opened

2016-01-11T23:26:30+00:00

There are some unfreed rpmmi pointers in printDepList() function; this happens when the package have null as the requirement. This patch fixes these unfreed pointers and add small changes to keep consistency with some variables. [YOCTO #8028] (From OE-Core rev: da7aa183f94adc1d0fff5bb81e827c584f9938ec) Signed-off-by: Mariano Lopez Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

rpmresolve: ignore null requires

2014-09-03T15:00:28+00:00

It is not a problem if a package requires nothing (similar to RDEPENDS is null), for example, these packages depends on nothing: [snip] alsa-conf-base base-files eglibc-binary-localedata-en-us xserver-xf86-config [snip] The rpmresolve-native's algorithm is: ===fake code for pkg in pkg1, pkg2, pkg3: rc = get_req(pkg) return rc ===fake code Suppose of the 3 pkgs requires null: - We are lukcy if pkg1 or pkg2 is null, nothing happend. - We are *not* lukcy if pkg3 is null, and will get the error when "INHERIT += 'buildhistory'": ERROR: Cannot get the package dependencies. Command '/path/to/x86_64-linux/usr/bin/rpmresolve -t /path/to/var/lib/rpm' returned 1: This patch fixes the problem. (From OE-Core rev: 2f234160ff4e9eccd8794a31df851b96328f6b74) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

rpmresolve: fix reporting of multiple matches error

2012-10-03T16:18:30+00:00

We were mistakenly writing what was meant to go to stderr into the output file, so when the "Multiple matches" error showed we weren't actually seeing the matches printed. Also change the wording of the "Unable to find package..." to "Unable to resolve package..." instead so that it makes more sense if it is printed after the "Multiple matches" error. (From OE-Core rev: c26542eb4e8707b9639ec309a44809a728839db8) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

rpmresolve: improve debug output

2012-08-15T13:26:43+00:00

Rename rpmresolve's -d option to -t and make -d enable debug output; add a -o option to specify the output file (so rpm debug output doesn't go to the output file) and also add a little more detail to some of the error messages. (From OE-Core rev: 163dd734d79fd7040b48b10bca6fde28460ac20c) Signed-off-by: Paul Eggleton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

rpmresolve: Ensure we call the rpm relocation code at init

2012-08-14T08:34:12+00:00

We need to call rpmcliInit to ensure the rpm relocation code is called and it correctly honours the relocation environmental variables. We can drop the ReadConfigFiles call since the cliInit does this for us. (From OE-Core rev: eb17fdc1461953382360635480f12357eac4dc43) Signed-off-by: Richard Purdie

buildhistory: improve performance of image info collection

2012-07-29T09:16:15+00:00

Reduce the number of calls to the packaging tool, especially in the case of rpm, using helper utilities to gather the required information more efficiently where possible. (From OE-Core rev: d0b8a98c5b46c305afd389fc862b3bf0c6f1eaab) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

classes/rootfs_rpm: improve speed of RPM rootfs construction

2012-07-29T09:16:14+00:00

Improve the performance of the RPM backend during do_rootfs by performing most of the package name to file resolution in a separate utility written in C, processing the entire list of packages at once rather than running rpm on the command line which loads the RPM database for every package. (From OE-Core rev: 9135d351ba7cb21e50239d2b310565680bd4fdca) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie