From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire: update to 0.3.43
Date: Mon, 21 Mar 2022 16:12:51 +0100 [thread overview]
Message-ID: <20220321151251.J2-0vHg8vO0_yq5AKK8VHjPn34iXO1cNKstGB7tMhRg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34904@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/pull/34904#issuecomment-1074022941
Comment:
alpine builds wireplumber with
```
provides="pipewire-session-manager"
provider_priority=0
```
and then pipewire with `-Dsession-managers=[]` accompanied
`install -Dm755 "$srcdir"/pipewire-launcher.sh "$pkgdir"/usr/libexec/pipewire-launcher`
by the launcher script
```
#!/bin/sh
# We need to kill any existing pipewire instance to restore sound
pkill -u "${USER}" -fx "/usr/bin/pipewire -c pipewire-pulse.conf" 1>/dev/null 2>&1
pkill -u "${USER}" -fx /usr/bin/pipewire-media-session 1>/dev/null 2>&1
pkill -u "${USER}" -fx /usr/bin/wireplumber 1>/dev/null 2>&1
pkill -u "${USER}" -fx /usr/bin/pipewire 1>/dev/null 2>&1
exec /usr/bin/pipewire &
# wait for pipewire to start before attempting to start related daemons
while [ "$(pgrep -f /usr/bin/pipewire)" = "" ]; do
sleep 1
done
if [ -x /usr/bin/wireplumber ]; then
exec /usr/bin/wireplumber &
elif [ -x /usr/bin/pipewire-media-session ]; then
exec /usr/bin/pipewire-media-session &
fi
[ -f "/usr/share/pipewire/pipewire-pulse.conf" ] && exec /usr/bin/pipewire -c pipewire-pulse.conf &
```
Would this work in void?
next prev parent reply other threads:[~2022-03-21 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 10:38 [PR PATCH] " st3r4g
2022-01-06 16:34 ` steinex
2022-01-07 1:27 ` [PR PATCH] [Closed]: " ahesford
2022-01-07 1:28 ` ahesford
2022-02-19 22:01 ` prez
2022-02-21 9:13 ` st3r4g
2022-02-21 11:47 ` prez
2022-02-21 16:26 ` st3r4g
2022-02-21 16:34 ` st3r4g
2022-02-21 17:45 ` prez
2022-02-21 17:49 ` prez
2022-02-21 17:51 ` prez
2022-03-21 15:12 ` dkwo [this message]
2022-03-21 15:44 ` ahesford
2022-03-26 20:17 ` prez
2022-03-26 20:26 ` Duncaen
2022-03-26 20:30 ` prez
2022-04-13 20:17 ` dkwo
2022-04-14 15:54 ` 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=20220321151251.J2-0vHg8vO0_yq5AKK8VHjPn34iXO1cNKstGB7tMhRg@z \
--to=dkwo@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).