From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] create pipewire-session-manager alternative group
Date: Sat, 18 Nov 2023 21:57:02 +0100 [thread overview]
Message-ID: <20231118205702.LrxLlyIUmZvkbEDJc3CFSpR-Eo1R9JdiW9KXw7MahTc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46960@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/46960#issuecomment-1817640035
Comment:
I tested this PR on pipewire version 0.3.84 with the conditional execution statements included. Unfortunately, conditional execution does not work the way I thought it did. If wireplumber is started in a file in `/usr/share/pipewire/pipewire.conf.d` and in another file/link in a different priority directory two instances of wireplumber will start, even with the conditional statements.
The mechanics of how those work aren't especially well documented. Given this section in the man page for `pipewire.conf`:
> Array of dictionaries. Each entry in the array is dictionary
> containing the path of a program to execute on startup and
> optional args.
>
> This array used to contain an entry to start the session manager
> but this mode of operation has since been demoted to development
> aid. Avoid starting a session manager in this way in production
> environment.
I don't think this behavior would be supported by upstream. However, given the persistent confusion around pipewire I would still support automatically starting wireplumber with the alternatives line and breaking the link, since that does work.
Also, since `/usr/share/pipewire/pipewire.conf.avail` already contains `10-rates.conf` and `20-upmix.conf`, should we consider changing the number prefixes for the files this PR would move to that directory?
next prev parent reply other threads:[~2023-11-18 20:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 19:11 [PR PATCH] " classabbyamp
2023-10-29 20:07 ` ahesford
2023-10-29 20:08 ` classabbyamp
2023-10-29 20:09 ` [PR PATCH] [Updated] " classabbyamp
2023-10-29 20:35 ` ahesford
2023-10-30 20:02 ` oreo639
2023-10-30 20:03 ` oreo639
2023-10-30 20:05 ` oreo639
2023-10-30 20:06 ` oreo639
2023-10-30 20:28 ` oreo639
2023-10-30 20:30 ` oreo639
2023-10-31 2:26 ` cinerea0
2023-10-31 2:46 ` oreo639
2023-10-31 2:46 ` oreo639
2023-11-18 20:57 ` cinerea0 [this message]
2024-02-17 1:44 ` github-actions
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=20231118205702.LrxLlyIUmZvkbEDJc3CFSpR-Eo1R9JdiW9KXw7MahTc@z \
--to=cinerea0@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).