Re: [poky] dnf5 and libdnf5 target release?
Frede Braendstrup <[email protected]> Fri, 15 Aug 2025 06:45:33 +0000
| Newsgroups | org.yoctoproject.lists.poky |
|---|---|
| Message-ID | <w7mjh7otgu4t7ngtdlbakw47beveqk5oshn6mkaejd33wxiwlz@qkmbrhbairvd> |
On Wed, Aug 13, 2025 at 01:01:33PM +0200, Alexander Kanavin wrote: > On Wed, 13 Aug 2025 at 12:25, Niko Mauno <[email protected]> wrote: > > On related note, about 5 weeks ago we briefly tried out if using dnf5 would yield any improvement in do_rootfs() turnaround time -- which it didn't (later on realized others seemed to also have expressed their surprise on lack of dnf5 performance improvement over dnf4 in some online discussion threads). > > I'm not surprised. The bulk of do_rootfs is creating a repository > index (not done by dnf), resolving dependencies (not done by dnf), and > unpacking and writing out .rpm content (also not done by dnf). Dnf5 > might feel snappier in interactive command line sessions, but > otherwise the whole project seems somewhat misguided. For context, I wasn't after performance improvements, but rather the native dbus interface provided by dnf5. I would be fine with just the feature set, but I'll find another way, Thanks. Frede
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJHy75INGducqKI4mZPwPSika/xoFAmie14kACgkQZPwPSika /xpnQQ//TwYEvvE8GBUrOK2ogUuDo9dc5ahu++cGDnpr2egl8P/XIpuj2OSGCuOG BH801UN6vTrKG0tM3nxZ9ogsEhB1nfByeEhj5zn73JVGP5QdG3DVX2IhkUpCY0GA /BHj8bEYl0K/+LFWA4CgZZr7rexdbczq47ikwAQZENORfgO7y0n8T64ZZbmzN6Ou u4jC6rkw9FFylpIGIRwPL6EwAaPaMg/nVKXdoDHC8WjG0hfPOF5yN4KEXjstQV4k LvS9k29fu+SSymX4ZYdbs2DB/ixiMvvGadn1kum67inikXZQGNIKUczfHeEmoNEJ ufUiBHWOomUtk7fDotTebnhlQe0sNIdFVCEVKRD2EeX9gUPOVnJKVLIhBqg7ZZt9 S9TfhZYSmUSjNMY+HzKbA4tm44hsCjyCwecHef8/3bnlJeVrblWIwFQnToyarYrJ O0/capeCAEDeaJKVu5X9KWnp/mKqbn0JvEXANAUJrkUo17PC5Cjzact/sjmVYKm4 0elJEUPzIAZRZ1Tgh02gdg/heCjXnFEQIqrXD3ot7IYZc1QFPf3H7D7vNJtKOzer Yv5S0hqxoaOEu9GgpL/fmtjoEgRsIRz2oY1e077pW66EsTvAcsi1IUjtFg14B7pu eAZsqke15/0uHLhk/KEZ0qrn9/ye0WCu+bZl/6/jlHRz5Bau9Zw= =Pe2Y -----END PGP SIGNATURE-----