Le jeudi 13 novembre 2014 à 10:54 +0100, Johannes Meixner a écrit :
Hello,
On Nov 12 18:58 Stanislav Brabec wrote (excerpt):
https://bugzilla.opensuse.org/show_bug.cgi?id=843526#c1 ----------------------------------------------------------------------- you can't use presets since they don't apply on for upgrade, only for new package installation (and it is not flexible enough for wha you want, I think).
you will probably need to handle the migration on your own, with explicit systemctl enable calls. -----------------------------------------------------------------------
Good grief! This means the systemd-presets-branding-* package is curently basically useless because a package must of course also work in case of updates.
No, it isn't. You want presets to do something different that what they are. Presets are doing exactly what their name imply: it is a preset, ie a default value. You obviously don't want this default value to be applied when packages are updated, overriding sysadmin changes. Case not handled currently in presets is when a preset file is introduced for a particular package which is already installed. People versatile in RPM and bash are welcome to help to fix that (filetriggers like in Mageia RPM would be great to automate that but AFAIK, they haven't landed in upstream RPM yet) General upgrade case from sysvinit to systemd service is properly handled (sysvinit initscript status is applied instead of preset in the initial migration). -- Frederic Crozat Project Manager Enterprise Desktop SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org