[OE-core] why would systemd-systemctl-native need underlying sysvinit?
Robert P. J. Day
rpjday at crashcourse.ca
Mon Feb 24 19:05:53 UTC 2020
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
========================================================================
More information about the Openembedded-core
mailing list