From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] pipewire, wireplumber, pulseaudio: move system services to /usr/share/examples/PKGNAME/sv/
Date: Mon, 29 May 2023 23:21:56 +0200 [thread overview]
Message-ID: <20230529212156.OMrpIreaO-TNj0rmE5COKXaS4uasuJWyH1UqQSUpovk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44141@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/44141#issuecomment-1567526996
Comment:
This is fine, but I think it might be better to completely remove the pipewire-pulse and wireplumber services, modify the (now example) pipewire service to wrap it in `dbus-run-session`, and tell people that want to use it that they should make pipewire launch pipewire-pulse and wireplumber via the proposed example config snippets.
This probably requires `control/t` and the pgrphack (`chpst -P`) trick in the current wireplumber service to make a best effort to kill all children.
This is essentially how I run a pipewire system service, and it is much more reliable and straightforward than trying to manage multiple services.
next prev parent reply other threads:[~2023-05-29 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 19:28 [PR PATCH] " classabbyamp
2023-05-29 19:56 ` [PR PATCH] [Updated] " classabbyamp
2023-05-29 20:35 ` classabbyamp
2023-05-29 21:21 ` ahesford [this message]
2023-05-29 21:57 ` classabbyamp
2023-05-29 21:58 ` classabbyamp
2023-05-30 2:03 ` [PR REVIEW] " ahesford
2023-05-30 2:03 ` ahesford
2023-05-30 2:14 ` [PR PATCH] [Updated] " classabbyamp
2023-05-30 2:46 ` [PR PATCH] [Merged]: " classabbyamp
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=20230529212156.OMrpIreaO-TNj0rmE5COKXaS4uasuJWyH1UqQSUpovk@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).