Goal

• As a user, I want to call the `dnf4` command run DNF 4 on RHEL 9, 10, and Fedora systems, so that habits/instructions/scripts will apply across systems.
• As a user, I want be able to install DNF 4 by dnf install dnf4 (or microdnf install dnf4)

Acceptance criteria

• python3-dnf package should provide `dnf4` so `dnf install dnf4` works
• python3-dnf package should provide symlink from /usr/bin/dnf4 to /usr/bin/dnf-3

Background

As of DNF 4.16.2, /usr/bin/dnf4 is a symlink to /usr/bin/dnf-3, which is the DNF binary provided by the python3-dnf package. The symlink was added so that users and scripts could easily and explicitly call DNF 4 as opposed to DNF 5 (which provides /usr/bin/dnf5), regardless of which package provides /usr/bin/dnf. dnf4 is more obvious to users than dnf-3 (which refers to "DNF 4 with Python 3").

As of https://github.com/rpm-software-management/dnf/pull/2190, python3-dnf also Provides: dnf4 so users can simply install dnf4 (e.g. with microdnf or dnf5) and not have to know that DNF 4 is provided by the package named python3-dnf.

The symlink and provides should be backported to as many systems as possible so scripts calling /usr/bin/dnf4 work everywhere, and dnf install dnf4 works everywhere.