From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.43
Date: Thu, 14 Apr 2022 17:54:07 +0200 [thread overview]
Message-ID: <20220414155407.5djOBGdrPjgHVmfPmz0UOFITLui4DnksJ6uY5etUvYo@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: 925 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/34904#issuecomment-1099329240
Comment:
Disabling the default session manager or separating it into a subpackage just leaves pipewire broken until you install one of the session managers and isn't really a workable solution. I think the only way to really manage this, short of upstream internalizing wireplumber (which I still think they should do, if it's the "official" session manager for pipewire), would be to create a meta package from an external template that depends on both pipewire and the preferred session manager; then we just have to tell people to install `pipewire-void` or something instead of just the pipewire package.
Of course, this update would break existing setups unless we violate our naming conventions and move pipewire to "pipewire-core" or something and name the meta-package "pipewire".
prev parent reply other threads:[~2022-04-14 15:54 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
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 [this message]
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=20220414155407.5djOBGdrPjgHVmfPmz0UOFITLui4DnksJ6uY5etUvYo@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).