pipewire: update to 0.3.65#41846
Conversation
|
This PR was only able to be submitted without significant patching because the devs released a new version of pipewire-media-session compatible with this version of pipewire. It took them a week to do so, and their release notes indicate that they may not do so again. As such I would like to draw attention to this PR that splits p-m-s out: #38521. |
|
Temporarily marking as draft as I test other, non-p-m-s patches linked in the release notes. |
|
For reasons I outlined in #38521 (comment), I think we should decide how we want to handle p-m-s after the 0.3.64 release. Based on that decision, we should use this bump to ensure continuity while also providing an |
|
I've added an |
|
Documentation on how to use wireplumber is missing from the handbook, so before telling people they should use it, we should document it. |
|
.65 is released now |
|
I've added wireplumber's desktop file. I have to test if 0.3.65 still allows p-m-s to be built. If it does should I change this PR to use 0.3.65 and we shift removing p-m-s to 0.3.66? EDIT: 0.3.65 has no problems building p-m-s with our current templates. Still need to do functionality testing. |
|
If 0.3.65 works with p-m-s, go ahead and bump this. I want to give the INSTALL.msg time to sink in and hopefully get people to transition to wireplumber. We can keep building p-m-s and extend the warning for a few releases if it works without patching. |
|
p-m-s build correctly locally and CI indicates it builds correctly elsewhere as well. |
|
There has been a lot of bikeshedding around pipewire, and I suspect there will continue to be more as we iron out the wrinkles in wireplumber documentation. None of that changes the fact that pipewire-media-session will soon become unmaintainable and we should drop it eventually. People should have the maximum possible notice that this will happen, even if the docs aren't quite ready. |
Closes: void-linux#41846 [via git-merge-pr]
Testing the changes