Re: systemd/sysvinit switches (was [meta-systemd][PATCH 1/2] Delete systemd class)

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

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

On Fri, Apr 12, 2013 at 11:46:16AM +0100, Burton, Ross wrote:
> Hi Andreas,
> 
> On 12 April 2013 09:56, Andreas Müller <schnitzeltony@googlemail.com> wrote:
> > OK - just in case I have spare cycles to start this: I am afraid I
> > lost overview regarding distro features. I found systemd and sysvinit
> > which can be set both - still correct?
> >
> > Ross could you please link me to the information how the use case 'I
> > want to build for both init-systems but let image decide which one to
> > use' is set up.
> > Sorry I didn't follow the last changes in detail because of other
> > issues (and personally I just use sysvinit).
> 
> It's in the manual!  Okay, only just, and it's still being worked on:
> 
> http://www.yoctoproject.org/docs/1.4/dev-manual/dev-manual.html#selecting-an-initialization-manager
> 
> (obviously the DISTRO_FEATURES = "systemd" bit is wrong, but you can
> see what the intention is)

for systemd-only case it should also recommend:

# sysvinit scripts are often missing in recipe
BAD_RECOMMENDATIONS += "update-rc.d"

Because at least dbus/udev are missing sysvinit scripts without sysvinit in
DISTRO_FEATURES and postinst scripts are failing when there is
udpate-rc.d but not script which it is trying to enable..

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

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