init: we don't need no systemd with sysvinit

That is, no need to pull in systemd as syslogd-daemon provider when an unspecified one has been requested by interactivesystem or anything else. The tricky issue is that THE_LISTS will get expanded separately and too late to specify a particular provider which will have been auto-chosen while expanding e.g. BASE_PACKAGES.

init: we don't need no systemd with sysvinit
b2a1befe · Michael Shigorin · f43d68ce · b2a1befe
Commit b2a1befe authored Sep 09, 2013 by Michael Shigorin
Hide whitespace changes
Inline Side-by-side

Showing with 3 additions and 0 deletions

config.mk features.in/init/config.mk +3 -0

No files found.
--- a/features.in/init/config.mk
+++ b/features.in/init/config.mk
@@ -5,8 +5,11 @@ use/init:
 	@$(call add_feature)
 	@$(call add,THE_LISTS,$$(INIT_TYPE))

+# THE_LISTS is too late when BASE_PACKAGES have pulled in
+# the wrong syslogd-daemon provider already
 use/init/sysv: use/init
 	@$(call set,INIT_TYPE,sysvinit)
+	@$(call add,BASE_PACKAGES,syslogd)

 ### i-f should be dropped as soon as rootfs scripts are effective there
 use/init/systemd: use/init