+++ This bug was initially created as a clone of Bug #1654659 +++ Description of problem: When installing dnf into a container image, it is preferable to use the systemd_ordering macro. According to https://fedoraproject.org/wiki/Packaging:Scriptlets: If a package is suitable for installation without systemd (in a container image, for example) and does not require any of the systemd mechanisms such as tmpfiles.d, then the systemd_ordering macro MAY be used instead of the systemd_requires macro. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
A PR against master https://src.fedoraproject.org/rpms/dnf/pull-request/14 and f29 backport https://src.fedoraproject.org/rpms/dnf/pull-request/15
Please, can you create PR against our upstream repository https://github.com/rpm-software-management/dnf ? We are maintaining the spec file there. Btw, are you aware whether this %{?systemd_ordering} macro is also usable on RHEL 7?
@Marek, will update the PR target, thanks! I think adapting this particular change request for RHEL7 may be a good idea, but wouldn't buy a lot, as other components, like iptables, iputils, rsyslog, puppet and more things will still be relying on systemd via its RPM specs.
Here is a new PR target https://github.com/rpm-software-management/dnf/pull/1315
Thanks, I'll look into it.
Closing because of https://github.com/rpm-software-management/dnf/pull/1315#issuecomment-462321911
Folks, perchance, do you know if there is a way to fix that to allow dnf leveraging the ordering macro? For containerized OpenStack, we really do not want to pull in systemd & deps for all containers only because we install packages with dnf there.