On Thu, 30 Jul 2020 at 11:47:51 +0100, Simon McVittie wrote: > pipewire will need a transition from 0.2.x to 0.3.x at some point, > allowing remote desktop support in GNOME to be re-enabled. This is an > API and ABI break, although the API breaks appear to be small enough > that some packages support both versions with some #if conditions. > > A prerequisite for all this is to get pipewire 0.3 through NEW and into > experimental (#954022).
It's now available in experimental. > - weston currently only supports Pipewire 0.2, and will need either > https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/456, > or that feature being disabled if it isn't considered important I've opened a bug. weston in experimental already has Pipewire disabled (it will need 0.3 available before it can be re-enabled). > - krfb and xdg-desktop-portal-kde appear to support both APIs upstream, > but will need some simple packaging changes to switch the dependency I've opened bugs. I'll try test-rebuilds of these soon if the KDE team don't get there first. I don't use KDE myself, so I can't really test them beyond that. > - mutter currently has remote desktop support disabled, but can > re-enable it after Pipewire 0.3 becomes available > > - xdg-desktop-portal will need new upstream release 1.7.x, or the Pipewire > features being disabled (1.7.x is already in experimental, with its > Pipewire support disabled for now because it needs Pipewire 0.3.x) Both of these have pipewire support enabled in experimental (although this is not a blocker for the transition - we can leave it disabled in unstable until the transition is over). > - gnome-remote-desktop will need new upstream release 0.1.8, and as far > as I understand it, is non-functional without Pipewire support that > matches what mutter uses This is now available in experimental too. It will need to be uploaded to unstable as part of the transition. smcv