On Fri, 2012-10-19 at 11:00 +0200, Bastien Nocera wrote: > Hello, > > I intend on making systemd a hard requirement for the power plugin in > gnome-settings-daemon. There is a lot of interactions and external > factors involved in making policy decision about power. This makes the > power plugin one of the more fragile parts of the system, with things > like DPMS, screensaver activation, screen locking, brightness control, > suspend policy, battery information exporting, all handled in the same > codebase. > > Using systemd to request suspends means that: > - things work out of the box when people do not use GNOME (no need to > install acpid which then conflicts with GNOME) > - inhibitions are per-system instead of per-user > - application get more information about suspending > - simplify the power plugin's codebase a great deal > > The patches I will commit are here: > https://bugzilla.gnome.org/show_bug.cgi?id=680689
Could you please list the systemd interfaces, methods, properties, and signals that you are planning to use so that non-systemd distros can evaluate what to do? In Gentoo, for example, we need to decide whether it's feasible to create a sufficient non-systemd implementation of these interfaces on top of consolekit and acpid, or whether booting with systemd really will become a hard requirement for us in 2013. _______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
