On Wed, Feb 08, 2012 at 10:28:12AM -0200, Otavio Salvador wrote: > On Wed, Feb 8, 2012 at 10:14, Koen Kooi <[email protected]> wrote: > > > Images with sysvinit will be working the same as before, just with > > libsystemd-logind.so.X being installed. Images with systemd get working > > session tracking. > > > > AFAIK polkit uses consolekit or systemd. In case you build it with systemd > you break consolekit support. > > However a stronger point IMO is that some changes, for one or another init > system, might involve specific compilation options and thus making their > runtime incompatible as it's the case of polkit. Usually people will want > one or another init system and I see no gain in have both available. > > Forcing user to use a bbappend to have one working well is the wrong way.
I think that only usable alternative _if it works_ is to build polkit linked always to libsystemd-logind.so.X and force users of sysvinit to use small part of systemd (libsystemd-logind.so.X packaged in systemd-logind). Then we could keep add --enable-systemd to polkit etc., but if this breaks stuff which worked with consolekit, then distro policy would be better. Cheers, -- Martin 'JaMa' Jansa jabber: [email protected]
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
