Le lundi 03 septembre 2012, à 21:52 +0200, Dominique Leuenberger a écrit :
On Mon, 2012-09-03 at 20:45 +0100, Cristian Morales Vega wrote:
The goal is really: let's not distract ourselves with fixing bugs for an init system we do not care for... and as long as we ship it, any bug report against it is legit;
So the only practical change you are proposing is to officially make it fair play to close any bug where the problem happens when using SysInitV but not when using SystemD? You have my vote.
Well, on the 'gnome side' for example that will also mean 'enabling systemd' support at full, wherever possible (which in turn means not relying on ConsoleKit in most placed, but using systemd-login and the likes). SystemD handles the seats anyway...
Dominique is not explaining the full story here ;-) Because we need to keep compatibility with sysvinit, there are several packages that we don't build with systemd support. Of course, it means we're losing features. One example is https://bugzilla.novell.com/show_bug.cgi?id=777096 But it also means we're in a situation that is actually not that well tested for upstream. Dominique found bugs in gdm that were not hitting the upstream developers because they were using systemd support in gdm, and not us. Those issues are only going to become more common with time. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org