sys-apps/sysvinit installs a bunch of tools not strictly related to sysvinit functionality which are used elsewhere, like pidof or sulogin.
We'd really appreciate if those tools could be split out into sysvinit-tools or something like that, so that systemd could depend on those tools while systemd-sysv-utils would block just the core sysvinit package.
Ah, and I mean the following tools:
/sbin/fstab-decode (not necessarily)
but not shutdown and related tools which rely on /dev/initctl.
I see that mountpoint was moved from sysvinit to util-linux. Is there
any possibility of working with the upstreams for these tools and moving
all of the tools mgorny mentioned over to util-linux?
there's always the possibility. all it takes is an e-mail to the util-linux/sysvinit lists asking.
(In reply to comment #1)
> Ah, and I mean the following tools:
> /sbin/fstab-decode (not necessarily)
> but not shutdown and related tools which rely on /dev/initctl.
Of these tools, the following are now in util-linux git:
Which only leaves the following:
there are talks of moving the kill utils upstream. this will sort itself out as newer versions of these packages are released.
(In reply to comment #5)
> there are talks of moving the kill utils upstream. this will sort itself
> out as newer versions of these packages are released.
Thanks for thoughtfully closing a blocker for a few other bugs.
(In reply to comment #6)
glad i could help
util-linux 2.22 is in the tree now and has absorbed sulogin/utmpdump
+1 for this.
We've been waiting for quite a while now. How about just splitting mentioned binaries into a separate ebuild (let's call it sysvinit-tools)?
Reopening since the problem didn't magically fix itself.
this bug is full of useless crap. if you have specific requests, file bugs for them (like enabling XXX tools in util-linux-XXX and disabling them in sysvinit). i'm not splitting sysvinit up, and if a tool hasn't been migrated out of sysvinit into some other package yet, then take it up with the respective upstream.