Andrei Borzenkov wrote:
В Tue, 11 Nov 2014 16:37:32 +0100 Stanislav Brabec <sbrabec@suse.cz> пишет:
I think the while point of presets is that they are external policy provided by independent authority. If package is going to install preset that always enables some service, package can just as well simply enable it in postinstall script, no?
Preset is a higher level of systemd setup: 1. systemctl start/stop sets the current service state 2. systemctl enable/disable sets the service state to active/inactive state. 3. systemctl preset sets the service to the proposed default state. Using systemctl enable should be reserved to system admin. It is should not be used in package post scripts, as it overwrites state defined by the system admin. Package should use presets. Then %service_add_post is sufficient. It does one time set to preset, and on the next update, service will stay in the previous state, i. e. if system admin decides to turn off the service, the customization will be kept. Ideally, all services should have a reasonable preset. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz Lihovarská 1060/12 tel: +49 911 7405384547 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org