Re: [PR PATCH] [Merged]: pipewire: update to 0.3.28

[ericonr <ericonr@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 3792 bytes --]

There's a merged pull request on the void-packages repository

pipewire: update to 0.3.28
https://github.com/void-linux/void-packages/pull/31012

Description:
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->

- The main change here is the move of default configs to `/usr/share`. `xbps` handled this well in my case (I had all default configs, which were deleted as expected). Can anyone verify that modified configs are left?
- I have briefly tried the filter-chains (`pipewire -c filter-chain/<X>.conf` runs a pipewire client that creates these "effect nodes") and they require ladspa plugins (one is not even packaged I think) but I don't think they should be hard dependencies. Also, some are borked still (e.g. `demonic.conf` ~~currently only works with a `audio.channels = 1` workaround~~ patch imported).

<details>
<summary>File diff</summary>

```
--- /tmp/old    2021-05-20 01:30:21.627554276 +0200
+++ /tmp/new    2021-05-20 01:30:37.523553285 +0200
@@ -1,14 +1,3 @@
-/etc/pipewire/client-rt.conf
-/etc/pipewire/client.conf
-/etc/pipewire/jack.conf
-/etc/pipewire/media-session.d/alsa-monitor.conf
-/etc/pipewire/media-session.d/bluez-monitor.conf
-/etc/pipewire/media-session.d/media-session.conf
-/etc/pipewire/media-session.d/v4l2-monitor.conf
-/etc/pipewire/pipewire-pulse.conf
-/etc/pipewire/pipewire.conf
-/etc/pipewire/media-session.d/with-jack
-/etc/pipewire/media-session.d/with-pulseaudio
 /usr/bin/pipewire
 /usr/bin/pipewire-media-session
 /usr/bin/pipewire-pulse
@@ -165,6 +154,22 @@
 /usr/share/man/man1/pw-mon.1
 /usr/share/man/man1/pw-profiler.1
 /usr/share/man/man5/pipewire.conf.5
+/usr/share/pipewire/client-rt.conf
+/usr/share/pipewire/client.conf
+/usr/share/pipewire/filter-chain/demonic.conf
+/usr/share/pipewire/filter-chain/sink-dolby-surround.conf
+/usr/share/pipewire/filter-chain/sink-eq6.conf
+/usr/share/pipewire/filter-chain/sink-matrix-spatialiser.conf
+/usr/share/pipewire/filter-chain/source-rnnoise.conf
+/usr/share/pipewire/jack.conf
+/usr/share/pipewire/media-session.d/alsa-monitor.conf
+/usr/share/pipewire/media-session.d/bluez-monitor.conf
+/usr/share/pipewire/media-session.d/media-session.conf
+/usr/share/pipewire/media-session.d/v4l2-monitor.conf
+/usr/share/pipewire/media-session.d/with-jack
+/usr/share/pipewire/media-session.d/with-pulseaudio
+/usr/share/pipewire/pipewire-pulse.conf
+/usr/share/pipewire/pipewire.conf
 /usr/bin/pw-midiplay -> /usr/bin/pw-cat
 /usr/bin/pw-midirecord -> /usr/bin/pw-cat
 /usr/bin/pw-play -> /usr/bin/pw-cat
```
</details>