EsounD needs to be added to Meson or dropped
We support EsounD only with Autotools and not with Meson. As we're going to drop Autotools, we'll either have to add EsounD support to Meson or drop the EsounD stuff entirely.
If we drop EsounD, here are some things that need to be done:
-
Don't enable module-esound-protocol-tcp in paprefs. -
The gsettings database may contain a module-esound-protocol-tcp entry even if paprefs has been updated, assuming that the new paprefs version doesn't actively disable the module. Actively disabling the module in paprefs doesn't really make sense, because that won't do anything as long as paprefs isn't updated or the user doesn't run paprefs. I think module-gsettings needs to be hacked to ignore module-esound-protocol-tcp (I say "hacked", because currently it's generic in the sense that it doesn't have knowledge of what modules it's dealing with). -
writeToGSettingsRemoteAccess()
inpaprefs.cc
usesname0
/args0
for module-native-protocol-tcp,name1
/args1
for module-esound-protocol-tcp andname2
/args2
for module-zeroconf-publish. If we drop the esound entry, eithername1
/args1
is left unset, in which case we need to ensure that module-gsettings can handle the list jumping from 0 to 2, or if we change it so that module-zeroconf-publish usesname1
/args1
, then we need to ensure that no bad things can happen during update due toname1
/args1
changing meaning.