Github messages for voidlinux
 help / color / mirror / Atom feed
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 18:45:51 +0100	[thread overview]
Message-ID: <20220221174551.wLYN1Tl7GwTCywKt2s9CnOqGhKnbVo7ye3LcEE73Dn0@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: 1268 bytes --]

New comment by prez on void-packages repository

https://github.com/void-linux/void-packages/pull/34904#issuecomment-1047111490

Comment:
If it is already deprecated and we must make the switch at some point (might as well do it early then - I doubt something will change about pipewire and wireplumber being separate projects upstream and the resulting cycle) , the way I see it, we have two options:
1. Enabling `-Dsession-managers="[ 'wireplumber' ]"`, which pulls in wireplumber and enables the relevant entry in the default configuration file, making wireplumber a subpackage and telling users to install it together with pipewire in the documentation for a functional pipewire setup.
2. Alternatively, figuring out how to ship it without media-session and a context.exec entry (building with session-managers `=[]` doesn't seem to have that effect), keeping the wireplumber package as it as and adding the same bit of documentation.

>Probably a bug.

I think this due to `context.exec` being an array, so it gets appended and you end up with both being executed. I would be against recommending to override the whole configuration file, and it's not something I want to do myself, since I don't keep up with changes well and I don't expect many users do.

  parent reply	other threads:[~2022-02-21 17:45 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
2022-02-21 16:26 ` st3r4g
2022-02-21 16:34 ` st3r4g
2022-02-21 17:45 ` prez [this message]
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=20220221174551.wLYN1Tl7GwTCywKt2s9CnOqGhKnbVo7ye3LcEE73Dn0@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).