From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: why would systemd-systemctl-native need underlying sysvinit?
Date: Mon, 24 Feb 2020 14:05:53 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.2002241402001.5567@localhost.localdomain> (raw)
in midst of migrating old YP layer to newer one and running across
all sorts of oddities. in this case, in current master branch of
oe-core, we have:
recipes-bsp/keymaps/keymaps_1.0.bb:PACKAGE_WRITE_DEPS_append = "
${@bb.utils.contains('DISTRO_FEATURES','systemd sysvinit','systemd-systemctl-native','',d)}"
recipes-core/psplash/psplash_git.bb:PACKAGE_WRITE_DEPS_append = "
${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd-systemctl-native','',d)}"
recipes-core/dbus/dbus_1.12.16.bb:PACKAGE_WRITE_DEPS +=
"${@bb.utils.contains('DISTRO_FEATURES','systemd sysvinit','systemd-systemctl-native','',d)}"
recipes-core/initscripts/initscripts_1.0.bb:PACKAGE_WRITE_DEPS_append = "
${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd-systemctl-native','',d)}"
recipes-kernel/modutils-initscripts/modutils-initscripts.bb:PACKAGE_WRITE_DEPS_append = "
${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd-systemctl-native','',d)}"
i'm curious as to why, in some cases, systemd-systemctl-native
requires *both* systemd and sysvinit to be contained in
DISTRO_FEATURES, but not in other cases. the migration section to YP
2.3 talks only about systemd.
thoughts?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2020-02-24 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 19:05 Robert P. J. Day [this message]
2020-02-24 19:14 ` why would systemd-systemctl-native need underlying sysvinit? Alex Kiernan
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=alpine.LFD.2.21.2002241402001.5567@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.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