Github messages for voidlinux
 help / color / mirror / Atom feed
From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] pipewire: split p-m-s into separate package, do not autostart session manager by default
Date: Wed, 25 Jan 2023 16:54:53 +0100	[thread overview]
Message-ID: <20230125155453.pALcLUxOBRkAMG_NTDPRiEPkvSz1jpjgCx8ItXcJEUY@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: 1921 bytes --]

There's a closed pull request on the void-packages repository

[RFC] pipewire: split p-m-s into separate package, do not autostart session manager by default
https://github.com/void-linux/void-packages/pull/38521

Description:
This proposes major changes to the handling of PipeWire session managers.

The PipeWire developers recommend the use of WirePlumber, but this is inconvenient with the current pipewire package.
In this PR I aim to improve the UX of void pipewire users by:

* splitting pipewire-media-session into a standalone package
* adding conflicts between pipewire-media-session and wireplumber

**The most immediate implication is that Void users who are using the default configuration (pipewire-media-session) and upgrade to this new pipewire version without further intervention will have their setups broken.** There will be no session manager running and pipewire will not function correctly. A news post will likely be needed to ensure that users are well informed of how to proceed.

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


  parent reply	other threads:[~2023-01-25 15:54 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
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 ` CameronNemo [this message]
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=20230125155453.pALcLUxOBRkAMG_NTDPRiEPkvSz1jpjgCx8ItXcJEUY@z \
    --to=cameronnemo@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).