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

[Koen Kooi <koen@dominion.thruhere.net>]

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

Op 07-02-12 16:55, Otavio Salvador schreef:
> On Tue, Feb 7, 2012 at 13:12, Andreas Müller 
> <schnitzeltony@googlemail.com>wrote:
> 
>> * These are my first python experiences - suggestions welcome. * In
>> local.conf (or in distro) the configuration variable INIT_MANAGER 
>> selects the initmanager to be build into an image. When changing the
>> selection, a build from scratch is required. INIT_MANAGER currently
>> defaults to systemd (see image.bbclass and initmanager.bbclass) * In
>> systemd.bbclass debug messages were left in to have a better overview 
>> what's going on. * An additional patch series goes out for
>> meta-angstrom. * This is a huge RFC which might cause serious impacts.
>> What I have already detected after a build from scatch is that
>> /var/lib/opkg is missing in the image (although it can be found in
>> libopkg.ipk). I will spend the next days with my new friend
>> buildhistory (thanks for this!!).
>> 
> 
> I've looked at your changes and they does seem to be a good base for 
> further work:
> 
> * The init system ought to be a DISTRO_FEATURE (as sysvinit ought to be
> too IMO) * I'd use rootfs generation to install ${PN}-${INIT_SYSTEM}
> packages for packages being installed

Those are really good suggestions!

> * I'd like to see sysvinit packages splitted onto ${PN}-sysvinit as well

This would require extra logic to install -sysvinit if -systemd is missing.

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk8xSx8ACgkQMkyGM64RGpGsZwCeN/ZmCXRJ1frrajkUyuYTaZjV
R9MAniJVOkSvJKdriTWW+K4oJdGZOyZ0
=jPg1
-----END PGP SIGNATURE-----