Cc @jtojnar

I thought that socket activation was working by default when package was added to systemd.packages. If systemd.user.sockets.pipewire.wantedBy = [ "sockets.target" ]; is necessary, let's merge it.

Though, maybe it would be nice to create some sort of abstraction (e.g. systemd.services.pipewire.socketActivatable = true). Also what is the point of disabling socket activation, why would anyone want that?

I thought that socket activation was working by default when package was added to systemd.packages. If systemd.user.sockets.pipewire.wantedBy = [ "sockets.target" ]; is necessary, let's merge it.

It's the same as any systemd system service not being activated simply by adding the package to systemd.packages but needing wantedBy = [ "multi-user.target" ];.

Though, maybe it would be nice to create some sort of abstraction (e.g. systemd.services.pipewire.socketActivatable = true).

That would indeed be neat - we should do something like this for all socket activatable services.

Also what is the point of disabling socket activation, why would anyone want that?

We have several other services that support socket activation but where it is configurable - this was added here as an option to be in line with those. I cannot, however, see why anybody would want to use any of the services that support socket activation and not use socket activation..