5 Jun
2019
5 Jun
'19
5:01 a.m.
Hi,
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?
Thorsten
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
5 Jun
5 Jun
5:09 a.m.
On Wed, Jun 5, 2019 at 6:01 AM Thorsten Kukuk <kukuk(a)suse.de> wrote:
Hi,
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
matter.
--
真実はいつも一つ！/ 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
5:43 a.m.
Hi,
On Wed, Jun 05, Neal Gompa wrote:
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.
Ok, so we don't need it. Due to the dependencies, you cannot have
systemd early in the transaction. We solved this in other ways,
so that it does not matter.
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
matter.
Ok, so we don't need it. Due to the dependencies, you cannot
have systemd early in the transaction to create user, so we solved
it in another way (convert sysusers configs to useradd options).
Thorsten
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
638
days inactive
638
days old
2 comments
2 participants
participants (2)
-
Neal Gompa -
Thorsten Kukuk