https://bugzilla.novell.com/show_bug.cgi?id=725917 https://bugzilla.novell.com/show_bug.cgi?id=725917#c20 Ruediger Meier <sweet_f_a@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |WONTFIX --- Comment #20 from Ruediger Meier <sweet_f_a@gmx.de> 2011-11-12 19:12:44 UTC --- How about making systemd-sysvinit and systemd-sysvinit(In reply to comment #18)
I consider blacklisting - zypper lock or from inside the YaST UI - an approach we should not recommend to our users.
On the other hand installing something just to deinstall it is IMO an absolutely inacceptable workflow which I wouldn't teach anybody. I'd rather rsync the blacklist across my host pool to be safe. Maybe there is another way without blacklisting? What about zypper in systemd-sysvinit before zypper up
I expect sysvinit to vanish completely in two or three releases as soon as the systemd stack settles more and more.
Hope not.
Over all the decision - as much as I don't like it - is the right approach. We have to focus on one technical solution and make this solution a nicely and smooth working one. That's what Frederic is working hard on. It's nor our obligation to help him as much as possible to make systemd smoothly fly with the next release.
Personally I don't have any use case for systemd so I can't really help except supporting bug reports where systemd breaks sysvinit. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.