On Thu, Mar 5, 2020 at 7:06 AM Marcin Juszkiewicz
W dniu 04.03.2020 o 19:03, Daniel Mach pisze:
> Hello everyone, I'm pleased to announce start of DNF 5 development.
> Microdnf is becoming important because it's part of
> many containers due to its small footprint.
[root@puchatek hrw]# ldd /bin/microdnf |wc -l
hrw@j13-qrep-04:ceph-12.2.11$ ldd /usr/bin/apt|wc -l
Apt's library dependencies are a lie if you look just at /usr/bin/apt,
as it relies very heavily on subprocessing for core functionality.
You'd need to check and add the dependencies of the helper binaries
that are required for apt functionality. Last I checked with 1.9.10,
it's fairly comparable.
Are there plans for picodnf then? Or cutting amount of
libraries used by microdnf?
My problem with DNF is Python. There is a huge amount of
packages which need to be in proper state to be able to use
dnf. I remember when I did some experiments with RHEL7 and
managed to get to the point where 'yum' was unable to help
as Python was broken.
Micro DNF is in C (using glib/gobject) today and would be in C++ in
the future. The transition from C to C++ will allow the GNOME library
ecosystem to be fully dropped as a dependency from the DNF stack. That
is substantial baggage that will finally go away.
真実はいつも一つ！/ Always, there's only one truth!