Feature Request: better handling of multilib install/upgrade requests

[michel-slm]

When managing a multilib system with a configuration management system like Chef, there is often an issue because recipes might try to handle a package without being multilib aware

(e.g. package 'foo' action :upgrade translates to Chef invoking dnf to install (not upgrade) the specific version it figures out to be the latest - but if a version of foo is installed already for a different architecture (e.g. i686) the operation normally fails with a file conflict between the new foo.x86_64 and the old foo.i686)

Would it make sense to have DNF5's semantics - both when invoked via command line and via the APIs - default to "if you ask me to install or update a package, do the install/update across all architectures that are already installed on the system"?

If this is not made into the default, but there is an option in dnf.conf that can be enabled, that would work as well.

[Conan-Kudo]

In DNF4, this was a configurable behavior using the multilib_policy= option in dnf.conf(5). Effectively multilib_policy=best did this. According to dnf5.conf(5), it is also the default behavior for DNF5.

So something isn't right...