From: prez <prez@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.43
Date: Mon, 21 Feb 2022 12:47:28 +0100 [thread overview]
Message-ID: <20220221114728.m_VfpTCohgqofRl13LF_JoHRHPgQJACDQxZrgJ9FNUk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34904@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
New comment by prez on void-packages repository
https://github.com/void-linux/void-packages/pull/34904#issuecomment-1046792155
Comment:
> Would work, but it's ugly. For example, it forces a rebuild of both every time. It is mainly intended for developers, not distros.
I see. Shipping it with media-session but documenting how to switch would be best then, probably.
On that note, how are you enabling wireplumber, in case you're running it? Either due to the precedence of files in `pipewire.conf` or the fact that array sections are appended, I can't seem to be able to specify wireplumber to run instead of media-session by dropping a .conf file into `~/.config/pipewire/pipewire.conf.d/` that overwrites only the `context.exec` section - and I do not want to have a global configuration in /etc or modify the provided files in /usr/share.
Apologies for hijacking this PR.
next prev parent reply other threads:[~2022-02-21 11:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 10:38 [PR PATCH] " st3r4g
2022-01-06 16:34 ` steinex
2022-01-07 1:27 ` [PR PATCH] [Closed]: " ahesford
2022-01-07 1:28 ` ahesford
2022-02-19 22:01 ` prez
2022-02-21 9:13 ` st3r4g
2022-02-21 11:47 ` prez [this message]
2022-02-21 16:26 ` st3r4g
2022-02-21 16:34 ` st3r4g
2022-02-21 17:45 ` prez
2022-02-21 17:49 ` prez
2022-02-21 17:51 ` prez
2022-03-21 15:12 ` dkwo
2022-03-21 15:44 ` ahesford
2022-03-26 20:17 ` prez
2022-03-26 20:26 ` Duncaen
2022-03-26 20:30 ` prez
2022-04-13 20:17 ` dkwo
2022-04-14 15:54 ` 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=20220221114728.m_VfpTCohgqofRl13LF_JoHRHPgQJACDQxZrgJ9FNUk@z \
--to=prez@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).