http://bugzilla.suse.com/show_bug.cgi?id=968405 http://bugzilla.suse.com/show_bug.cgi?id=968405#c64 Egbert Eich <eich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mls@suse.com) --- Comment #64 from Egbert Eich <eich@suse.com> --- The code: %if "%{stop_on_remove}"=="default" \ test "$DISABLE_STOP_ON_REMOVAL" = yes -o \ "$DISABLE_STOP_ON_REMOVAL" = 1 && exit 0 \ test -f /etc/sysconfig/services && . /etc/sysconfig/services \ test "$DISABLE_STOP_ON_REMOVAL" = yes -o \ "$DISABLE_STOP_ON_REMOVAL" = 1 && exit 0 \ %endif implies, that in 'default' mode, we want to honour $DISABLE_STOP_ON_REMOVAL not only set in /etc/sysconfig/services but coming from other sources (spec-file, global environment) as well. Do we want this - or do we want two separate modes ('legacy' and 'default')? Ie: 'legacy' - (no option flag) with the described behaviour and 'default' - (option flag -d) where we ignore $DISABLE_STOP_ON_REMOVAL from any other sources than /etc/sysconfig/services In the light of comments #38, #40 and #41 I'd like to get Michael's opinion. -- You are receiving this mail because: You are on the CC list for the bug.