On Mon, Oct 1, 2012 at 9:14 AM, Bill Kenworthy <[email protected]> wrote: > Does LXDE have a position on systemd/udev etc? > > I am thinking of the apsect where gnome will, and where its being talked > about that any desktop will have no choice but to move to systemd > exclusively to function at all. Currently gentoo is moving to > stubs/scripts and work arounds to avoid replacing what is a more > flexible init system. > > I moved from (what was for me a disaster) gnome 3 to LXDE and being on > Gentoo, I am looking to avoid the systemd and udev direction being > pushed. > > BillK
This is a real issue, but the answer to the questions depends on the popularity and acceptance of the proposed solution among existing distros. I personally want to avoid unnecessary layers and complexity, but it's harder and harder to make things KISS. DBus is a good example. Now it's hard to find a system working completely without dbus and newer glib/gio has built-in dbus support. Whether you use it or not, it's built-into glib so even if you don't use it, it's still there. Gnome people constantly moves many of the so-called gnome technologies to glib, gio, and gtk+ and make them part of these base libraries. Since we're using the library, we get the gnome technologies/dependencies automatically by this way. So some things are not determined by ourselves. One of the best example must be glib/gio. To make it function properly, you needs gvfs (replacement of gnome-vfs) and gsettings (replacement for gconf). Gvfs actually requires dbus and udisks2, which depends on polkit and udev. By using gio to manage devices, we get dependency on polkit + dbus + udisks2 + udev no matter we like them or not. But what if we don't use them? Our program won't work properly with other existing gtk+/glib programs and will has some additional permission problems. Instead of reinventing another system doing the same thing and cause incompatibility, it's apparently a better idea to use the solutions provided by glib/gio/gtk+. Free software is all about choice, but the current condition is all about having no choices. LXDE does not requires these dependency itself, but if the dependencies are acquired indirectly by gtk+/glib, there is no way to avoid them. That means, if in the future, glib/gio/gtk+ requires systemd to function properly, it's hard for us to avoid that. If they don't make this a hard dependency and keep gtk+/glib independent from systemd, we can avoid using it if we have better alternatives. If all major distros are using systemd, it's hard for us not to use it. Of course we need to support other non-Linux OSes when possible. If in the future only fedora is using systemd and it's not widely accepted, we should not have a hard dependency on it. Being a small project, we don't have many choices, though. Not using existing solutions means we have create and maintain alternatives ourselves, which is very labor-intensive and time-consuming. So the answer to the question is, that depends. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
