FS#64071 - [base] Please remove systemd-sysvcompat or have it as optional dependency at max
Attached to Project:
Arch Linux
Opened by Dirk (dsohler) - Wednesday, 09 October 2019, 15:56 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 08 December 2019, 11:17 GMT
Opened by Dirk (dsohler) - Wednesday, 09 October 2019, 15:56 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 08 December 2019, 11:17 GMT
|
Details
Since systemd-sysvcompat is a package that is needed for
outdated systems to provide backwards compatibility with the
initscripts that were discontinued and removed 7 years ago
it should not be a hard dependency of the base package.
Instead of "forcing" the installation of an extremely old and technically not needed package the official installation documentation should be altered in a way that it describes how to add "init=/usr/lib/systemd/systemd" as a kernel parameter and how to shutdown/reboot/ etc. the system with systemctl. (Yes, I know how to "force" packages not being installed, but that is not the point of this issue.) |
This task depends upon
Closed by Dave Reisner (falconindy)
Sunday, 08 December 2019, 11:17 GMT
Reason for closing: Won't fix
Additional comments about closing: These are considered canonical command names and won't be going anywhere.
Sunday, 08 December 2019, 11:17 GMT
Reason for closing: Won't fix
Additional comments about closing: These are considered canonical command names and won't be going anywhere.
They are all links to either systemctl or systemd. We've still haven't decided on the final version for this, but I think it all points in the direction of having those links residing on the systemd package itself.
Telling users they should set init= by hand is insane. And, we only support systemd. Also, I don't get why you're complaining about a 5KiB package.
Merging the symlinks into the systemd package will simply result in other bugs being filed. The systemd package has the nice feature right now of being able to co-exist with other init systems. it's not easy to uninstall systemd, in part because the packaging has changed numerous times and we've not enforced rebuilds to keep up with the various provides, etc. So, having the symlinks in a separate package to make you "commit" to systemd is a nice feature for everyone.
btw: I only use systemctl reboot and counterparts, so, in theory I could get away without a systemd-sysvcompat package.
sysvinit openrc eudev udev-openrc eudev-systemd dbus-openrc procps-ng-nosystemd syslog-ng-nosystemd udisks2-nosystemd consolekit polkit-consolekit upower-pm-utils udisks2-nosystemd desktop-privileges xorg-xwrapper acpid-openrc alsa-utils-openrc autofs-openrc consolekit consolekit-openrc cronie-openrc dbus-openrc cups-openrc displaymanager-openrc fuse-openrc haveged-openrc hdparm-openrc openssh-openrc samba-openrc syslog-ng-openrc avahi-openrc
Not sure about parabola or hyperbola, couldn't find links regarding migrating from Arch to them, as artix does.
One statement in an accessory sentence by one individual in one single issue not even related to "`systemctl xyz` vs. `xyz`" ... It's a bit of a stretch to say that systemd developers see this as primary interfaces. And according to the issue creator it is written in the manpage for `reboot` that those are "legacy commands available for compatibility only". I doubt that systemd devs see legacy commands that only exists for compatibility reasons as primary interface.
If those symlinks are really the primary interface (is this documented somewhere in official systemd documentation?) why are they not part of the systemd package? Were they moved into an own package by Arch devs and are actually part of upstream? And if so: Is this still needed in reality?
The man pages now state "These commands are implemented in a way that preserves compatibility with the original SysV commands."