TLDR: I want to know if I should include PulseAudio 4.0 in the win32 builds of X2Go Client 4.0.2.x. For testing, should I post a 4.0.1.2 build with PulseAudio 4.0, or post a HEAD build with it?
Mike#1 recently announced that "we are close to bumping X2Go Client to a new release series (4.0.2.x)" https://lists.berlios.de/pipermail/x2go-dev/2014-January/006847.html I have managed to compile PulseAudio 4.0 (the latest) for win32. I also managed to compile 3.0. The builds are here: https://build.opensuse.org/project/show/home:mikedep333:branches:home:mkbosmans:mingw32:pulseaudio Unfortunately, neither 3.0 nor 4.0 fixed the issue in bug 363 and described on this wiki page: http://wiki.x2go.org/doku.php/wiki:bugs:pulsetestmatrix In other words, we will still need to ship "interims" builds with PulseAudio 0.9.6 to fix that bug. I am hoping that this bug might be fixed in PulseAudio HEAD/master, but I am still trying to compile it. Even if it is fixed, that doesn't mean we will necessarily ship HEAD/master. I also am not aware of any x2goclient-relevant win32 improvements to PulseAudio since 1.1. So I want feedback if we should include PulseAudio 4.0 in X2Go Client 4.0.2.x. My gut feeling is "yes, because we should stay current with upstream." I also want to know if for the sake of testing, I should post a 4.0.1.2 build with PulseAudio 4.0, or post a HEAD build with it. I can do the former within 2 days, and the latter within 5 days or so. I have done a small amount of testing of 4.0; I haven't seen any regressions. -Mike#2
_______________________________________________ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
