Re: [PATCH 2/2] local.conf.sample: Document HOW-TO enable systemd or busbox to replace sysvinit

[Tanu Kaskinen <tanuk@iki.fi>]

On Fri, 2016-01-22 at 20:49 +0000, Khem Raj wrote:
> OE core provides systemd,busybox as options for system init system along
> with sysvinit being the default. Document the needed settings to enable
> systemd and busybox as options if user wishes.
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>  meta/conf/local.conf.sample | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample
> index a662f4d..b760546 100644
> --- a/meta/conf/local.conf.sample
> +++ b/meta/conf/local.conf.sample
> @@ -209,6 +209,23 @@ PACKAGECONFIG_append_pn-qemu-native = " sdl"
>  PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
>  #ASSUME_PROVIDED += "libsdl-native"
>  
> +#
> +# Use busybox/mdev for system initialization
> +#
> +#VIRTUAL-RUNTIME_dev_manager = "busybox-mdev"
> +#VIRTUAL-RUNTIME_login_manager = "busybox"
> +#VIRTUAL-RUNTIME_init_manager = "busybox"
> +#VIRTUAL-RUNTIME_initscripts = "initscripts"
> +#VIRTUAL-RUNTIME_keymaps = "keymaps"
> +#DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
> +
> +#
> +# Use systemd for system initialization
> +#
> +#DISTRO_FEATURES_append = " systemd sysvinit"
> +#DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"

Why is sysvinit included in both DISTRO_FEATURES and
DISTRO_FEATURES_BACKFILL_CONSIDERED? My understanding is that
BACKFILL_CONSIDERED only makes sense when the value is not included in
DISTRO_FEATURES.

-- 
Tanu