From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.70
Date: Sat, 06 May 2023 05:47:27 +0200 [thread overview]
Message-ID: <20230506034727.VBe9Zj9M8q1xhmnqgFxdwug3-nBthmk-f_sisWsXYzA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43574@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/43574#issuecomment-1537035971
Comment:
Upstream has been telling us unequivocally for a long time to stop using this program. We need to rip off this Band-Aid and stop patching our configs to do things we shouldn't have been doing in the first place. We are now at the point where we are causing problems for upstream because our users are complaining to them when our problematic configuration changes break. This is inconsiderate and should not be allowed to continue.
The marginal benefit of keeping p-m-s going and adopting the conditional change is that some users *who have not already switched to wireplumber* in the months we've been warning them to do so, but will *suddenly decide to do so before we drop p-m-s*, can do so with a drop-in configuration snippet that will become a no-op after we actually drop the session manager.
1. Those that have already switched to WirePlumber will have already shadowed the system configuration. This isn't a major issue, but can be a minor inconvenience because they may not notice other configuration changes that would have to be reconciled with their overrides.
2. All remaining users will still have their pipewire configuration break at some point in the future when p-m-s stops working properly.
next prev parent reply other threads:[~2023-05-06 3:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 17:35 [PR PATCH] " cinerea0
2023-04-22 17:49 ` cinerea0
2023-05-06 1:53 ` ahesford
2023-05-06 1:54 ` ahesford
2023-05-06 3:04 ` oreo639
2023-05-06 3:05 ` oreo639
2023-05-06 3:07 ` oreo639
2023-05-06 3:47 ` ahesford [this message]
2023-05-15 21:49 ` marmeladema
2023-05-17 18:17 ` cinerea0
2023-05-18 13:28 ` ahesford
2023-05-20 2:38 ` [PR PATCH] [Updated] " cinerea0
2023-05-24 17:10 ` [PR PATCH] [Closed]: pipewire: update to 0.3.71, drop pipewire-media-session ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230506034727.VBe9Zj9M8q1xhmnqgFxdwug3-nBthmk-f_sisWsXYzA@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).