From: Javyre <Javyre@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.17
Date: Mon, 30 Nov 2020 17:48:17 +0100 [thread overview]
Message-ID: <20201130164817.hzkWsJK7D75M4TYWUbDePC47Zd0yHn4UlSTwqBe4-Eo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26822@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
New comment by Javyre on void-packages repository
https://github.com/void-linux/void-packages/pull/26822#issuecomment-735905379
Comment:
I feel like it would be useful to have a runit service defined for pipewire.
Apparently the system daemon it generates [just runs it as user `pipewire`](https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/src/daemon/systemd/system/pipewire.service.in).
next prev parent reply other threads:[~2020-11-30 16:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 9:48 [PR PATCH] " st3r4g
2020-11-30 12:27 ` st3r4g
2020-11-30 12:28 ` st3r4g
2020-11-30 13:38 ` st3r4g
2020-11-30 13:41 ` st3r4g
2020-11-30 13:53 ` [PR PATCH] [Updated] " st3r4g
2020-11-30 15:09 ` [PR REVIEW] " ahesford
2020-11-30 15:44 ` st3r4g
2020-11-30 15:44 ` st3r4g
2020-11-30 15:46 ` st3r4g
2020-11-30 15:56 ` [PR PATCH] [Updated] " st3r4g
2020-11-30 16:01 ` st3r4g
2020-11-30 16:14 ` Javyre
2020-11-30 16:20 ` Javyre
2020-11-30 16:22 ` [PR REVIEW] " st3r4g
2020-11-30 16:23 ` st3r4g
2020-11-30 16:26 ` st3r4g
2020-11-30 16:26 ` st3r4g
2020-11-30 16:45 ` [PR REVIEW] " ericonr
2020-11-30 16:48 ` Javyre [this message]
2020-11-30 17:09 ` st3r4g
2020-11-30 19:21 ` st3r4g
2020-12-01 18:21 ` [PR REVIEW] " ahesford
2020-12-01 18:52 ` st3r4g
2020-12-01 19:14 ` ericonr
2020-12-01 20:39 ` [PR PATCH] [Merged]: " ahesford
2020-12-01 20:41 ` ahesford
2020-12-01 20:44 ` st3r4g
2020-12-02 20:13 ` gspe
2020-12-03 4:48 ` ahesford
2020-12-04 12:04 ` sirn
2020-12-04 12:37 ` st3r4g
2020-12-04 12:37 ` st3r4g
2020-12-04 12:42 ` st3r4g
2020-12-04 12:45 ` st3r4g
2020-12-04 13:18 ` sirn
2020-12-04 14:35 ` gspe
2020-12-04 15:11 ` 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=20201130164817.hzkWsJK7D75M4TYWUbDePC47Zd0yHn4UlSTwqBe4-Eo@z \
--to=javyre@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).