From 62e7e9c152ffde355c648fde98d717c395711178 Mon Sep 17 00:00:00 2001 From: Michael Shigorin Date: Mon, 29 Sep 2014 14:14:25 +0400 Subject: [PATCH] init: ban systemd when sysvinit has been requested The issue at hand is that interactivesystem pulls in network-config-subsystem and that one has several providers by now, systemd-networkd being one of them since recently (and pulling in systemd). Just the same problem as with systemd-journal; both might be fixed by reworking mkimage to allow for different package name resolution modes: - "slap everything together and resolve with one-shot" to handle conflictless situations (most of those); - "process multiple transactions to allow for conflicts" thus making it possible to include e.g. a few MTAs into the provided package base. Ensure that systemd is outside by explicitly telling so in the pkglist. --- pkg.in/lists/sysvinit | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pkg.in/lists/sysvinit b/pkg.in/lists/sysvinit index a8d076c6..e838d60b 100644 --- a/pkg.in/lists/sysvinit +++ b/pkg.in/lists/sysvinit @@ -1,3 +1,5 @@ sysvinit sysklogd interactivesystem +systemd-services- +systemd-