From: Adrian Bunk <bunk@stusta.de>
To: kai.kang@windriver.com
Cc: poky@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] defaultsetup.conf: enable select init manager
Date: Sat, 6 Jul 2019 15:08:10 +0300 [thread overview]
Message-ID: <20190706120810.GC1877@localhost> (raw)
In-Reply-To: <20190706095328.GA1877@localhost>
On Sat, Jul 06, 2019 at 12:53:28PM +0300, Adrian Bunk wrote:
> On Thu, Jul 04, 2019 at 09:45:19PM +0800, kai.kang@windriver.com wrote:
> > From: Kai Kang <kai.kang@windriver.com>
> >
> > Introduce a new variable INIT_MANAGER and create 3 init-manager-*.inc
> > files to configure init manager settings. Available values of
> > INIT_MANAGER are sysvinit, systemd and mdev-busybox. 'sysvinit' is set
> > by default for compatibility.
> >...
> > --- a/meta/conf/distro/defaultsetup.conf
> > +++ b/meta/conf/distro/defaultsetup.conf
> > @@ -23,3 +23,6 @@ PACKAGE_CLASSES ?= "package_ipk"
> > INHERIT_BLACKLIST = "blacklist"
> > INHERIT_DISTRO ?= "debian devshell sstate license remove-libtool"
> > INHERIT += "${PACKAGE_CLASSES} ${USER_CLASSES} ${INHERIT_DISTRO} ${INHERIT_BLACKLIST}"
> > +
> > +INIT_MANAGER ??= "sysvinit"
> > +require conf/distro/include/init-manager-${INIT_MANAGER}.inc
> >...
> > --- /dev/null
> > +++ b/meta/conf/distro/include/init-manager-sysvinit.inc
> > @@ -0,0 +1,6 @@
> > +# Use sysvinit for system initialization
> > +DISTRO_FEATURES_append = " sysvinit"
> > +DISTRO_FEATURES_BACKFILL_CONSIDERED_append = " systemd"
> > +VIRTUAL-RUNTIME_init_manager = "sysvinit"
> > +VIRTUAL-RUNTIME_initscripts = "initscripts"
> > +VIRTUAL-RUNTIME_login_manager = "busybox"
>
> I am not sure whether this can be fixed better, but this does break
> existing configurations that use a non-default init system.
>
> I just ran into a build issue with
> VIRTUAL-RUNTIME_init_manager = "systemd"
> since this now resulted in both sysvinit and systemd being attempted to
> be installed to the image.
>
> This was fixable in my configuration with
> -VIRTUAL-RUNTIME_init_manager = "systemd"
> +INIT_MANAGER = "systemd"
>
> This at least needs to be properly documented as a breaking change.
Looking at master-next, this problem is actually fixed for me with
meta: Improve handling of VIRTUAL-RUNTIME variables
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-07-06 12:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 13:45 [PATCH v7 0/2] Make systemd as default init manager kai.kang
2019-07-04 13:45 ` [PATCH 1/2] defaultsetup.conf: enable select " kai.kang
2019-07-06 9:53 ` Adrian Bunk
2019-07-06 12:08 ` Adrian Bunk [this message]
2019-07-06 12:31 ` richard.purdie
2019-07-08 9:28 ` Kang Kai
2019-07-08 10:01 ` ChenQi
2019-07-08 2:01 ` Kang Kai
2019-07-08 2:13 ` Kang Kai
2019-07-19 21:35 ` Burton, Ross
2019-07-19 22:28 ` richard.purdie
2019-07-22 1:37 ` Kang Kai
2019-07-22 23:26 ` Mittal, Anuj
2019-07-23 19:30 ` richard.purdie
2019-07-25 11:10 ` Kang Kai
2019-07-04 13:45 ` [meta-poky][PATCH 2/2] poky.conf: make systemd as default " kai.kang
2019-07-04 22:34 ` richard.purdie
2019-07-04 15:00 ` ✗ patchtest: failure for Make " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190706120810.GC1877@localhost \
--to=bunk@stusta.de \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox