Systemd Preset Policy
sergio at serjux.com
Sat Jul 25 21:41:55 UTC 2015
On Sáb, 2015-07-25 at 05:00 +0000, Zbigniew Jędrzejewski-Szmek wrote:
> On Sat, Jul 25, 2015 at 04:10:28AM +0100, Sérgio Basto wrote:
> > This kind of scriptlet still works on Fedora 22 (updated), on a new
> > installation ?
> Yes, that still works, but should be converted to the new way of doing
OK thanks for clear this up .
> So most likely you'd want to first file a bug against
> fedora-release (see below), and after it is resolved, modify your
> package to use %systemd_post.
> > Other wiki page shows that PackagePresets are from Fedora 18 ! 
> That is when this functionality was originally introduced. What changed
> now is that presets has become *the* official way to enable services by
> default. It is less convenient for packagers, but is more convenient for
> admins and products.
> > And what is the best way to set a preset for a service ? that we want
> > enable by default, when is installed .
> > Note: I'm asking this because I don't saw any example on package
> > guidelines.
>  shows the syntax in the spec file (common for all services), and 
> shows the additional steps which need to be taken for enabled-by-default
>  https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
>  https://fedoraproject.org/wiki/Packaging:DefaultServices#How_to_enable_a_service_by_default
The packages that I'm concerned about are in a third party repo . How we
may workaround this ? is to add one file
in /usr/lib/systemd/system-preset/ ?
Sérgio M. B.
More information about the devel