I see. Now that you mentioned the
::kde overlay, I found
drkonqi-6.3.91::kde, and yes, that ebuild has a hard dependency on systemd. Since the older drkonqi ebuild does not have such a dependency, I assume that the change was deliberate and that the newer drkonqi really does need systemd. In particular, I see in the
older 6.30.80 ebuild:
Code: Select all
-DWITH_SYSTEMD=OFF # non-systemd snapshot before it was made required
From that, it seems very likely that the ebuild maintainer knew exactly what he was doing when he put the hard dependency in the 6.3.91 ebuild. It is not a mistake due to incomplete information, but instead is a reflection of upstream's choice to require users to run systemd.
Your split-usr profile is relevant here only in that you cannot use systemd with split-usr (anymore), so if you did want to switch to systemd, you would need to migrate to merged-usr. Since you are opposed to using systemd, you can stay on split-usr.
I think your only options now are:
- Switch to systemd
- Ban use of drkonqi on this system