Bug#794692: Building xrdp PulseAudio modules for great remote desktop experience

Felipe Sateler fsateler at debian.org
Thu Oct 6 13:25:36 UTC 2016

Control: tags -1 = upstream help

(adding back the bug to CC).

On 6 October 2016 at 09:57, Dominik George <nik at naturalnet.de> wrote:
> Hi Felipe,
>> The situation has changed a bit: pulseaudio upstream is receptive to
>> shipping such headers provided they have a define that users
>> explicitly need to be set (so that people do not unsuspectingly use
>> it), because the module api is not easily stabilized at the moment. I
>> believe that this is just lacking someone that implement this at the
>> moment. So maybe the bug should be untagged wontfix.

I'm removing the wontfix tag. Tagged help as patches welcome.

> How would I go about that? Would I find out what APIs the module needs
> to build, then ask upstream to add them to their shipped header files,

What I remember from the last discussion with upstream is that they
are receptive to patches, but are not themselves working on it. So
s/ask upstream/propose a patch upstream/.

> then wait for them to find their way into the Debian pulseaudio-dev
> package?

I will probably put them in a separate package, but yes, that would be
the idea (I could be persuaded to backport the patch if the next
release is too far away).


Felipe Sateler

More information about the pkg-pulseaudio-devel mailing list