Mailinglist Archive: opensuse-packaging (116 mails)

< Previous Next >
Re: [opensuse-packaging] Packages enabling their systemd services at their own
On 12/11/2017 07:52 PM, Stefan Seyfried wrote:
Am 11.12.2017 um 16:14 schrieb Thorsten Kukuk:

the official mechanismus to enable systemd services by default during
installation is, to use the systemd preset functionallty.

Unfortunately, some packages still enable their services at their own
by calling systemctl enable in the %post install section. This will
break in the future for fresh installations!

Why? We have a problem with dependencies for systemd, dependency loops
and packages, where we are not able to enable them with the preset
mechanism during initial installation. The reason is, that systemd with
it's many dependencies can only be installed late, but some packages
have to be installed earlier. The same is true for build dependencies.

If we require a PreReq systemd for all packages having systemd units,
we will end in a dependency loop nightmare. Instead, we decided, that
we will call a systemctl preset-all in the %posttrans of
systemd-presets-branding-* packages for fresh installations.
So now I add "systemd-presets-branding-bluez" subpackage to bluez?
Any boilerplate code to use for this?

Yeah, same with syslog-ng. I can version update syslog-ng but can change
systemd support only if there is an example I can follow.



To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >