DNF5 delayed

Fedora packaging policy is such that dynamic linking is required (see e.g. https://lore.kernel.org/lkml/CAHk-=whs8QZf3YnifdLv57+FhBi... for a famous case). Dynamic linking is possible in rust, but without a stable ABI it's as far as I understand not really recommended or all that useful, except when exporting a C ABI. The same is kind of true for C++ except that the C++ ABI (at least with stdlibc++) is in practice fairly stable with a few notable exceptions.

I'm not sure there is an issue with a package manager updating itself unless it does something silly like reload shared libraries at run time. The replaced library is still going to be the one in its address space? I guess if you did something silly like updated libdnf without updating dnf that could in principle cause problems if the two become incompatible but that shouldn't be possible to do with dnf...