From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] pipewire: split p-m-s into separate package, do not autostart session manager by default
Date: Wed, 25 Jan 2023 15:53:10 +0100 [thread overview]
Message-ID: <20230125145310.KGsgK3OXJ5c76gti3eQFBNYdT0uUOwFcEnvj39iZxv0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38521@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/38521#issuecomment-1403743362
Comment:
It is pretty clear that upstream does not want people running p-m-s anymore:
> https://gitlab.freedesktop.org/pipewire/media-session/-/releases/0.4.2
I don't think p-m-s should be split into a subpackage; it should just be dropped with the (next) release of pipewire. At the very least, this means we should probably tack on an install message *now* to warn people that this will happen.
Wireplumber shouldn't depend on pipewire; in fact, the dependency should be the other way around when p-m-s is no longer an option (unless we have an alternative session manager packaged). Having the proper dependency relationship should minimize the pain of transition for users with the default configuration, but it creates a build cycle that we will have to break. Options include:
- Renaming pipewire to something like `pipewire-tools` or `pipewire-utils` and adding a standalone `pipewire` meta-package that pulls in `pipewire-tools` as well as `wireplumber`. This has the advantage that we don't really have to worry about syncing the build process between two artificially split packages. In fact, the meta can just get a dated version that we only bump when we need to.
- Alternatively, `libpipewire` and `pipewire-devel` could be split into a standalone package so that `wireplumber` can pull them in without the rest. This kind of sucks because we'll be forced to keep two packages synchronized.
- Coming up with some way to build `wireplumber` without the `pipewire-devel` dependency. Meh.
next prev parent reply other threads:[~2023-01-25 14:53 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 19:28 [PR PATCH] pipewire: use a conffile to autostart p-m-s CameronNemo
2022-08-17 19:20 ` [PR PATCH] [Updated] " CameronNemo
2022-08-20 22:22 ` pipewire: use a drop-in " paper42
2022-08-21 6:03 ` CameronNemo
2022-08-21 6:06 ` CameronNemo
2022-08-21 6:07 ` CameronNemo
2022-09-05 18:57 ` [PR PATCH] [Updated] " CameronNemo
2022-09-08 3:06 ` pipewire: update to 0.3.57, " ericonr
2022-09-08 5:28 ` CameronNemo
2022-09-08 5:30 ` CameronNemo
2022-09-20 12:21 ` CameronNemo
2022-09-20 12:29 ` Duncaen
2022-09-20 18:20 ` CameronNemo
2022-09-20 18:24 ` Duncaen
2022-09-20 18:30 ` Duncaen
2022-09-20 18:32 ` Duncaen
2022-09-20 18:35 ` Duncaen
2022-09-20 18:53 ` CameronNemo
2022-09-20 21:24 ` CameronNemo
2022-12-09 22:40 ` leahneukirchen
2022-12-09 22:53 ` JamiKettunen
2022-12-09 22:54 ` JamiKettunen
2022-12-09 23:04 ` JamiKettunen
2022-12-10 3:25 ` CameronNemo
2022-12-10 6:58 ` [PR PATCH] [Updated] " CameronNemo
2022-12-10 7:10 ` [PR PATCH] [Updated] [RFC] pipewire: split p-m-s into separate package, do not autostart session manager by default CameronNemo
2022-12-10 7:16 ` CameronNemo
2023-01-13 7:06 ` [PR PATCH] [Updated] " CameronNemo
2023-01-13 7:41 ` CameronNemo
2023-01-13 8:33 ` CameronNemo
2023-01-22 23:39 ` motorto
2023-01-23 3:58 ` oreo639
2023-01-23 4:05 ` oreo639
2023-01-23 4:15 ` oreo639
2023-01-23 4:19 ` oreo639
2023-01-23 4:20 ` oreo639
2023-01-23 4:21 ` oreo639
2023-01-23 4:24 ` oreo639
2023-01-23 4:31 ` oreo639
2023-01-23 4:34 ` oreo639
2023-01-23 4:36 ` oreo639
2023-01-23 4:39 ` oreo639
2023-01-23 5:42 ` oreo639
2023-01-23 6:08 ` oreo639
2023-01-23 6:09 ` oreo639
2023-01-23 6:42 ` oreo639
2023-01-23 6:45 ` oreo639
2023-01-23 6:45 ` oreo639
2023-01-23 6:46 ` oreo639
2023-01-23 6:47 ` oreo639
2023-01-23 6:48 ` oreo639
2023-01-23 7:22 ` oreo639
2023-01-23 8:02 ` oreo639
2023-01-23 8:02 ` oreo639
2023-01-23 8:02 ` oreo639
2023-01-23 8:03 ` oreo639
2023-01-23 8:04 ` oreo639
2023-01-23 8:05 ` oreo639
2023-01-23 8:05 ` oreo639
2023-01-23 8:05 ` oreo639
2023-01-23 8:05 ` oreo639
2023-01-23 8:08 ` oreo639
2023-01-23 8:09 ` oreo639
2023-01-23 9:10 ` oreo639
2023-01-23 22:30 ` CameronNemo
2023-01-23 22:30 ` CameronNemo
2023-01-25 14:53 ` ahesford [this message]
2023-01-25 15:40 ` CameronNemo
2023-01-25 15:52 ` ahesford
2023-01-25 15:54 ` ahesford
2023-01-25 15:54 ` CameronNemo
2023-01-25 15:54 ` [PR PATCH] [Closed]: " CameronNemo
2023-01-25 16:31 ` ahesford
2023-01-28 11:42 ` oreo639
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=20230125145310.KGsgK3OXJ5c76gti3eQFBNYdT0uUOwFcEnvj39iZxv0@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).