Systemd macros (f18+)
Bruno Wolff III
bruno at wolff.to
Thu Sep 13 12:47:43 UTC 2012
On Thu, Sep 13, 2012 at 09:10:45 +0200,
Lennart Poettering <mzerqung at 0pointer.de> wrote:
>In other words:
>A) There's one postinst script that invokes "systemctl enable"
>B) There's another one that does not invoke systemctl, and leaves the service off
>C) There's a third one that invokes "systemctl preset"
>In F16/F17 A and B are used. Some packages use A, most packages use B.
>In F18 only C is used. All packages use C.
>In F18 we have a macro that implements C. We have no macro that
>implements A or B.
>Now, you are asking me to provide a macro with the same name and
>functionality in F16/F17 as the one we introduced for F18, right? But
>how could we do this? If on F18 the macro implements C, what would it
>implement on F16/F17? Would it implement A? If so, it would be useless
>for all packages whose service needs to stay off after
>installation. Would it implement B? If so, it would be useless for all
>packages whose service needs to be enabled after installation.
>Of course we could introduce new macros for both A and B, so that we'd
>have three macros, covering all three operations. But who'd be helped
>with that? We should introduce new stuff only for new distros, and maybe
>backport it. But this would be adding completely new stuff to old
>distros that makes no sense anymore on new distros, and hence we
>shouldn't do it.
I believe the suggestions was to have macros for A and B that did A and B
on f16/f17 and did the same as C on F18+. That way a package could use
a single macro on all current releases. Then when f18 was the oldest
current release, packages could switch to using macro C for all releases.
More information about the devel