Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.70
Date: Sat, 22 Apr 2023 19:49:20 +0200	[thread overview]
Message-ID: <20230422174920.ewGqfuSoswwmZmIzLJIrJA430hSPOAegmgIqAoRV03Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43574@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

New comment by cinerea0 on void-packages repository

https://github.com/void-linux/void-packages/pull/43574#issuecomment-1518716034

Comment:
This release of pipewire added functionality to conditionally start a session manager. I want to draw attention to [this comment](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3160#note_1870332) by a pipewire dev on the issue that led to this feature being implemented, which references problems resulting from autostarting `pipewire-media-session`:

> Yes, the way you did will end up running both. You will need to fully override the main pipewire.conf file instead. Alternatively either convince your distro to:  
> * stop using dead software
> * adopt a launcher script or daemon like they should have long ago
> * just switch to a better distro (and, if no, you can keep your reasoning to yourself, I can already imagine them without you typing them out but it still needed to be said).

Given that pipewire contributors are now regularly referring to p-m-s as "dead software", I think we have three options:

1. Continue to leave things as they are.
2. Change the patch to only start p-m-s conditionally and update the documentation to reference the solution in the linked issue.
3. Drop p-m-s as in #41868, even though it still builds fine.

  reply	other threads:[~2023-04-22 17:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22 17:35 [PR PATCH] " cinerea0
2023-04-22 17:49 ` cinerea0 [this message]
2023-05-06  1:53 ` ahesford
2023-05-06  1:54 ` ahesford
2023-05-06  3:04 ` oreo639
2023-05-06  3:05 ` oreo639
2023-05-06  3:07 ` oreo639
2023-05-06  3:47 ` ahesford
2023-05-15 21:49 ` marmeladema
2023-05-17 18:17 ` cinerea0
2023-05-18 13:28 ` ahesford
2023-05-20  2:38 ` [PR PATCH] [Updated] " cinerea0
2023-05-24 17:10 ` [PR PATCH] [Closed]: pipewire: update to 0.3.71, drop pipewire-media-session 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=20230422174920.ewGqfuSoswwmZmIzLJIrJA430hSPOAegmgIqAoRV03Q@z \
    --to=cinerea0@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).