Sure, that's what libsystemd0 is. It's just a shared library, like libselinux1, that lets applications be compiled with systemd support. It doesn't depend on sy

Sure, that's what libsystemd0 is. It's just a shared library, like libselinux1, that lets applications be compiled with systemd support. It doesn't depend on systemd itself, or start up any daemons. It's quite possible to have a package that's compiled with support for two different logging systems, for example. In that case it would depend on the libraries for both of them, but would only actually use the one that is configured. On the other hand, it's possible an application actually does require systemd running to function, in which case it would depend on 'systemd' as well, not only 'libsystemd0'.