On 02/21/2018 10:47 AM, Igor Gnatenko wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Wed, 2018-02-21 at 10:24 +0200, Panu Matilainen wrote:
On 02/21/2018 10:12 AM, Panu Matilainen wrote:
On 02/20/2018 10:15 PM, Igor Gnatenko wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Tue, 2018-02-20 at 19:11 +0000, Peter Robinson wrote:
On Tue, Feb 20, 2018 at 1:11 PM, Igor Gnatenko
<ignatenkobrain@xxxxxxxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hey,
today I've split⁰ librpmsign from rpm-build-libs into its own
subpackage
rpm-
sign-libs.
Does this mean that the python bindings no longer depend on
rpm-build-libs and hence won't be pulled for a standard minimal
install and similar artifacts anymore?
Nope, it means that python bindings will depend *also* on
rpm-sign-libs 😉
Since bindings are monolitic, it's not possible to split them easily.
Actually you could split out build- and sign-bindings (together or
separately) from the main python bindings package. "import rpm"
intentionally lets the build- and sign-module imports to fail to allow
this so as long as the "submodules" depend on the main bindings it
should be ok.
Oh and BTW, the reason this hasn't been done is basically the same the
sign-libs hadn't been split up: in the past when I last looked at the
situation, there just was no benefit to doing so. Back then fedpkg was
present in buildroots, and yum + yum-utils used to be included in core
set (quite possibly "minimal" install as you know it today didn't even
exist), and yum itself dragged in a whole pile of gpg-related packages.
This probably still doesn't make much sense, dnf pulls in python3-rpm and
python3-gpg. In the end, both are pulling in gnupg2.
What about the minidnf thingie, does it pull gnupg2 in as well?
The other thing is the build-side dependencies: elfutils-libs and
file-libs. They're by no means big, but if you're going for the
absolutely bare minimum (container or otherwise) images...
- Panu -
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
