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

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]

On Wed, Feb 08, 2012 at 01:51:54PM +0100, Andreas Müller wrote:
> On Wed, Feb 8, 2012 at 1:14 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > That is why I want to make an exception for polkit and udisks to keep
> > initmanager selection an IMAGE_FEATURE combined with DISTRO_FEATURE. A
> > distro maintainer can then choose to support one or more initmanagers and in
> > the case for multiple it can be set per image.
> >
> > regards,
> >
> > Koen
> I haven't the point: why do we need such quirks to keep initmager an
> image feature? Could you please help me out here?
> 
> FYI one of my tests was to build the image I usually work with configured as
> 
> INIT_MANAGER = "sysvinit"
> 
> and systemd isn't build at all - so no need to take care at specific
> recipes: They will configure for what I (or the distro) want them.
> 
> Please see INIT_MANAGER as distro feature. I did not add it to the
> collection of DISTRO_FEATURES to avoid setting multiple initmanages.

For me it would allow to support palmpre* devices just by slightly
different image even when it has too old kernel for systemd.

If it's distro feature then we'll have to drop support or find some devs
still interested enough in palmpre* to port all patches to newer kernel
and support it.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]