From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] pipewire: update, add virtual session manager to pull in wireplumber without build cycle
Date: Wed, 24 May 2023 19:10:50 +0200 [thread overview]
Message-ID: <20230524171050.dkpt9-DE7lm6hF4VGczaHW06fpLDAAIgjIiMNZmwQVY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41868@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
There's a closed pull request on the void-packages repository
[RFC] pipewire: update, add virtual session manager to pull in wireplumber without build cycle
https://github.com/void-linux/void-packages/pull/41868
Description:
> **Note:** This is not really intended as an update to 0.3.64; instead, if there is enough support for this proposal, I think https://github.com/void-linux/void-packages/pull/41846 should be merged with an `INSTALL.msg` warning people that pipewire-media-session will be dropped in the next release and that they should make sure they have a working wireplumber configuration before then.
pipewire will not work without a session manager; the previously included pipewire-media-session has long been deprecated and is now abandoned [1]. Making pipewire depend on wireplumber would create a cycle, so the cycle is broken with a rename and a new metapackage:
1. Rename pipewire -> pipewire-utils to clear the pipewire name
2. New pipewire meta depends on pipewire-utils and wireplumber
The rename is a violation of policy but allows existing pipewire users to see the new meta as an update that will pull in an updated real pipewire alongside the now-required wireplumber.
Continuing the work of https://github.com/void-linux/void-packages/pull/38521.
[1] https://gitlab.freedesktop.org/pipewire/media-session/-/releases/0.4.2
prev parent reply other threads:[~2023-05-24 17:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 16:31 [PR PATCH] [RFC] pipewire: update, rename pipewire-utils, add new meta to pull in wireplumber ahesford
2023-01-25 16:49 ` [PR PATCH] [Updated] " ahesford
2023-01-25 16:51 ` ahesford
2023-01-25 21:32 ` cinerea0
2023-01-26 2:48 ` cinerea0
2023-01-26 2:49 ` [PR PATCH] [Updated] " ahesford
2023-01-26 2:53 ` ahesford
2023-01-26 2:56 ` ahesford
2023-01-26 14:06 ` [PR PATCH] [Updated] " ahesford
2023-01-26 14:08 ` ahesford
2023-01-26 14:08 ` ahesford
2023-01-28 14:35 ` [PR PATCH] [Updated] [RFC] pipewire: update, add virtual session manager to pull in wireplumber without build cycle ahesford
2023-01-30 20:51 ` ahesford
2023-02-04 2:35 ` ahesford
2023-02-04 12:17 ` ahesford
2023-02-04 19:01 ` ahesford
2023-05-06 1:48 ` github-actions
2023-05-06 1:55 ` ahesford
2023-05-24 17:10 ` ahesford
2023-05-24 17:10 ` 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=20230524171050.dkpt9-DE7lm6hF4VGczaHW06fpLDAAIgjIiMNZmwQVY@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).