3 ms·
If the dependency can be satisfied by systemd-shim, the package will depend on "systemd | systemd-shim". This means that if you have neither installed, systemd
by irl_ 10y ago
If the dependency can be satisfied by systemd-shim, the package will depend on "systemd | systemd-shim". This means that if you have neither installed, systemd would be installed. If you have systemd-shim installed then it's fine with that.
There are packages that really do depend on systemd, and so they would not have their dependencies satisfied.
If you really hate systemd that much that you want to put in effort to keep it out, I would seriously suggest putting in some contributions to alternative init systems and patches for software that requires systemd to have fallbacks to work on those init systems.
If you're desperately trying to keep systemd out of your system then maybe you shouldn't upgrade your system (think LTS releases) until you've figured out how your applications work with systemd.
systemd is not going away, posts like this are OK for those who have been hit with surprises, but anyone that thinks this ignoring systemd is a viable long term fix is delusional.
- daveguy 10y ago> anyone that thinks this ignoring systemd is a viable long term fix is delusional. As is anyone who doesn't acknowledge there are always alternatives in the open source world.
- vetinari 10y ago> As is anyone who doesn't acknowledge there are always alternatives in the open source world. That's why the GP wrote this: > I would seriously suggest putting in some contributions to alternative init systems and patches for software that requires systemd to have fallbacks to work on those init systems. The problems that systemd solves and others don't, won't get resolved by closing eyes and hoping for the best. They can get solved by writing code for those alternate init systems. As an example, is ConsoleKit working already, after all the years of neglect and ignorance of pleads of the desktop environment guys? (Of course not).