[oe] [meta-oe][RFC 00/27] systemd / initmanager rework

Koen Kooi koen at dominion.thruhere.net
Wed Feb 8 13:05:28 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 08-02-12 13:43, Martin Jansa schreef:
> On Wed, Feb 08, 2012 at 10:28:12AM -0200, Otavio Salvador wrote:
>> On Wed, Feb 8, 2012 at 10:14, Koen Kooi <koen at dominion.thruhere.net>
>> 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.

This is not really directed at Martin, but at the wider audience:

For the past 6 months I have been trying to make consolekit work:

http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-support/consolekit?id=eb828308b8e721e4ad7edbd15f47ecad22ee81cf

http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-support/consolekit?id=5608a748af2c754f60137ab7c3010ccce6bf9e40

And right now it still isn't working properly. Look real close at the first
commit; oe-core developers made a serious effort to make it
non-functional[1], only linking needed to succeeded. So please stop saying
CK will break, it already is broken.

Now back to the original discussion: support setting multiple init managers
in DISTRO_FEATURES and keep the final choice an IMAGE_FEATURE. The end
result: the integrator keeps the same freedoms and when having only a single
init manager in DISTRO_FEATURES things will slightly improve.

regards,

Koen

[1] To be fair, that was not their goal, but it was the end result. No
malice there, I verified :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk8ycxMACgkQMkyGM64RGpF/MwCfdLEnjLDnZDtN5VhPt0mDZRzi
LbcAn2aYuUZXcPkMRY2qfMYK2dgmSTC5
=sX7J
-----END PGP SIGNATURE-----





More information about the Openembedded-devel mailing list