pipewire: fix enableSystemd option

Setting enableSystemd to false did not disable systemd, because on
most Linux configurations, udev is an alias for systemd, so Pipewire
would still find libsystemd, and link
e.g. libpipewire-module-protocol-native against it.  With libsystemd
actually not available in the build environment, we need to set
-Dsystemd=disabled, which should also avoid this unintended automatic
systemd linkage in future.

Additionally, since udev was always an input, there was no point also
providing an eudev input.  udev is an alias for a udev implementation
appropriate for the platform (systemd, libudev-zero, or in future
libudev-devd).  eudev can still be used using an override:

	pipewire.override {
		enableSystemd = false;
		udev = eudev;
	}

So with this change, setting enableSystemd to false will disable
systemd-specific functionality in pipewire, but it will use systemd's
udev implementation (which might as well just be a more up to date
version of eudev), which matches the behaviour of other
enableSystemd/systemdSupport options in Nixpkgs, and in the case where
even systemd's udev implementation is for some reason too much,
that's configurable as well.

0 files changed, 0 insertions, 0 deletions