pipewire etc

Why do we need different policies for alsa, pipewire, and pulseaudio?  They 
all do the same things, why not just have an audioserver policy that supports 
all of them?

Why do we need an ifdef for server vs user operation of pipewire?  Why not 
just have a policy with a pipewire_t for the system daemon and pipewire_user_t 
for the user process?

https://wiki.archlinux.org/title/
PipeWire#Sharing_audio_devices_with_computers_on_the_network

For people wondering as I did why we even need a pipewire_user_t domain, the 
above section of the Arch Wiki documents sharing audio via Airplay and RTP 
among others - definitely need that isolated!

Is a pipewire_client_t domain just for the test program really useful?

It looks like the policy is well structured and replacing the cruft from years 
of support of alsa and pulseaudio is a good thing.  So I think we should go 
all the way and delete the separate policy for the old sound servers.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/