On Wed, Jun 5, 2019 at 6:01 AM Thorsten Kukuk <kukuk(a)suse.de> wrote:
Which sense should the RPM macro %systemd_ordering have?
In the current form, it's completly useless in my opinion.
For the %service_* macros, systemd is not needed. The preset packages
enabling services make sure that systemctl is installed before, but
the packages containing systemd service files either don't need it,
or the preset packages did made sure that it is already installed.
To solve the problem, that the tools used by %service_* macros are
installed: this is in the current form not guaranteed. If this works,
then only by accident, not by design. You only need to follow the
dependency chain to see that.
So which problem does this macro really solve?
If you need systemd to be early in the transaction if it is part of
the transaction (such as creating an installation), then it'll ensure
it's ordered early. This is mainly useful to ensure things like
systemd-sysusers works and such for VM environments, but doesn't
necessarily take effect in container bootstrap, where this doesn't
真実はいつも一つ！/ Always, there's only one truth!
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org