Comment Re:Systemd (Score 2) 182
But then, they included a DNS resolver, X11 auto configuration (which broke many desktop assumptions), user session management, syslog replacement, and the kitchen sink.
You realize systemd isn't a gigantic monolithic kitchen-sink binary, right? The service manager runs in PID 1, but things like logind, journald, networkd, resolved are all separate programs running in separate processes. And the auxiliary stuff is optional; if you don't want to use systemd's DNS resolver, don't install it. Plain old dhclient editing resolv.conf still works the same as always.
But including a package manager? Oh, come on, that is a bridge too far.
It's another separate program, and only relevant for distributions that are specifically designed to use it instead of a conventional package manager. If you're running something typical like Ubuntu or Arch or RHEL, systemd-sysupdate is not meant for you, and your distro likely won't even provide builds of it.
Package-based distributions have been around for a long time; we have good package managers now because the major ones have been in development for a quarter-century. RPM is a lot more robust now than it was back in 1997. Image-based distributions are a different approach that's new and experimental, so the systemd developers have taken a shot at advancing the state of the art for that kind of distribution model. They're not trying to change how traditional package-based systems install their updates.