* [sumo][PATCH] systemd: Expose resolv-conf alternative only when resolved is built
@ 2019-10-04 7:51 Alexandre Bard
0 siblings, 0 replies; only message in thread
From: Alexandre Bard @ 2019-10-04 7:51 UTC (permalink / raw)
To: openembedded-core@lists.openembedded.org; +Cc: Alexandre Bard
When systemd is built without internal resolver, it does not make
sense to expose it as a resolv-conf alternative and can even break
images where this alternative would be chosen, because of an
invalid symlink.
Signed-off-by: Alexandre Bard <alexandre.bard@netmodule.com>
---
meta/recipes-core/systemd/systemd_237.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/systemd/systemd_237.bb b/meta/recipes-core/systemd/systemd_237.bb
index a0e5d512e0..d3a6d52a73 100644
--- a/meta/recipes-core/systemd/systemd_237.bb
+++ b/meta/recipes-core/systemd/systemd_237.bb
@@ -548,6 +548,7 @@ python __anonymous() {
# TODO:
# u-a for runlevel and telinit
+ALTERNATIVE_${PN} = "init halt reboot shutdown poweroff runlevel ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'resolv-conf', '', d)}"
ALTERNATIVE_${PN} = "init halt reboot shutdown poweroff runlevel resolv-conf"
ALTERNATIVE_TARGET[init] = "${rootlibexecdir}/systemd/systemd"
--
2.20.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2019-10-04 7:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-10-04 7:51 [sumo][PATCH] systemd: Expose resolv-conf alternative only when resolved is built Alexandre Bard
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox