From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-video/pipewire/files/, media-video/pipewire/
Date: Sat, 17 Jun 2023 02:49:58 +0000 (UTC) [thread overview]
Message-ID: <1686970100.868c215ffeb611c667c3464fabd24c5ac59fff32.sam@gentoo> (raw)
commit: 868c215ffeb611c667c3464fabd24c5ac59fff32
Author: Alexis <flexibeast <AT> gmail <DOT> com>
AuthorDate: Thu Jun 15 01:06:47 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jun 17 02:48:20 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=868c215f
media-video/pipewire: Add gentoo-pipewire-launcher.1 man page
Closes: https://bugs.gentoo.org/908510
Signed-off-by: Alexis <flexibeast <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../pipewire/files/gentoo-pipewire-launcher.1 | 43 ++++++++++++++++++++++
...ewire-9999.ebuild => pipewire-0.3.71-r3.ebuild} | 2 +
media-video/pipewire/pipewire-9999.ebuild | 2 +
3 files changed, 47 insertions(+)
diff --git a/media-video/pipewire/files/gentoo-pipewire-launcher.1 b/media-video/pipewire/files/gentoo-pipewire-launcher.1
new file mode 100644
index 000000000000..d2c30dc961bc
--- /dev/null
+++ b/media-video/pipewire/files/gentoo-pipewire-launcher.1
@@ -0,0 +1,43 @@
+.TH "gentoo-pipewire-launcher" "1" "2023-06-15"
+.SH "NAME"
+gentoo\-pipewire\-launcher \- start instances of PipeWire, PipeWire-Pulse and WirePlumber
+.SH "SYNOPSIS"
+.BR gentoo\-pipewire\-launcher
+[restart]
+.SH "DESCRIPTION"
+\fIgentoo\-pipewire\-launcher\fR starts instances of PipeWire and
+WirePlumber.
+Two instances of PipeWire are started: one as the core sound-server, and
+one for PulseAudio emulation (cf.\&
+.BR pipewire-pulse (1)\fR).
+.PP
+It must be run in an environment with an active D-Bus session bus,
+i.e. one in which the
+.B DBUS_SESSION_BUS_ADDRESS
+environment variable is set appropriately.
+.PP
+\fIgentoo\-pipewire\-launcher\fR
+tries to avoid restarting, in order to avoid audio dropouts.
+However, a restart can be forced by calling
+\fIgentoo\-pipewire\-launcher\fR
+with an argument of \(oqrestart\(cq.
+.PP
+.B ${XDG_CONFIG_HOME}/gentoo\-pipewire\-launcher.conf
+can be used to specify absolute paths of files to which log output
+should be sent, by specifying values for one or more of the
+.B GENTOO_PIPEWIRE_LOG\fR,
+.B GENTOO_PIPEWIRE_PULSE_LOG\fR,
+and
+.B GENTOO_WIREPLUMBER_LOG
+variables, one per line.
+.SH "REPORTING BUGS"
+Please report bugs via https://bugs.gentoo.org/
+.SH "FILES"
+.TP
+.B ${XDG_CONFIG_HOME}/gentoo\-pipewire\-launcher.conf
+configures locations of files for log output.
+.SH "SEE ALSO"
+.BR pipewire (1),
+.BR pipewire-pulse (1),
+.BR wireplumber (1),
+.BR pipewire.conf (5)
diff --git a/media-video/pipewire/pipewire-9999.ebuild b/media-video/pipewire/pipewire-0.3.71-r3.ebuild
similarity index 99%
copy from media-video/pipewire/pipewire-9999.ebuild
copy to media-video/pipewire/pipewire-0.3.71-r3.ebuild
index 7289c71e58b0..33887a9e61c1 100644
--- a/media-video/pipewire/pipewire-9999.ebuild
+++ b/media-video/pipewire/pipewire-0.3.71-r3.ebuild
@@ -299,6 +299,8 @@ multilib_src_install_all() {
exeinto /usr/bin
newexe "${FILESDIR}"/gentoo-pipewire-launcher.in-r2 gentoo-pipewire-launcher
+ doman "${FILESDIR}"/gentoo-pipewire-launcher.1
+
# Disable pipewire-pulse if sound-server is disabled.
if ! use sound-server ; then
sed -i -s '/pipewire -c pipewire-pulse.conf/s/^/#/' "${ED}"/usr/bin/gentoo-pipewire-launcher || die
diff --git a/media-video/pipewire/pipewire-9999.ebuild b/media-video/pipewire/pipewire-9999.ebuild
index 7289c71e58b0..33887a9e61c1 100644
--- a/media-video/pipewire/pipewire-9999.ebuild
+++ b/media-video/pipewire/pipewire-9999.ebuild
@@ -299,6 +299,8 @@ multilib_src_install_all() {
exeinto /usr/bin
newexe "${FILESDIR}"/gentoo-pipewire-launcher.in-r2 gentoo-pipewire-launcher
+ doman "${FILESDIR}"/gentoo-pipewire-launcher.1
+
# Disable pipewire-pulse if sound-server is disabled.
if ! use sound-server ; then
sed -i -s '/pipewire -c pipewire-pulse.conf/s/^/#/' "${ED}"/usr/bin/gentoo-pipewire-launcher || die
next reply other threads:[~2023-06-17 2:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 2:49 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-17 20:00 [gentoo-commits] repo/gentoo:master commit in: media-video/pipewire/files/, media-video/pipewire/ Andreas Sturmlechner
2024-07-01 8:19 Sam James
2023-08-24 19:42 Sam James
2023-06-07 9:52 Sam James
2023-06-07 9:52 Sam James
2023-05-05 8:35 Sam James
2022-12-30 6:59 Sam James
2022-12-27 14:17 Sam James
2022-12-16 4:56 Sam James
2022-12-10 4:35 Sam James
2022-11-11 4:25 Sam James
2022-11-11 4:25 Sam James
2022-07-19 21:18 Sam James
2022-07-10 20:23 Sam James
2022-07-09 1:12 Sam James
2022-07-04 23:53 Sam James
2022-06-15 21:56 Sam James
2022-06-10 0:38 Sam James
2022-04-21 22:03 Sam James
2022-04-21 21:57 Sam James
2022-04-17 16:44 Sam James
2022-04-15 7:59 Sam James
2022-01-29 0:49 Sam James
2022-01-06 20:53 Sam James
2021-12-18 6:39 Sam James
2021-11-11 22:09 Sam James
2021-10-26 9:03 Sam James
2021-10-26 8:59 Sam James
2021-10-25 17:12 Patrick McLean
2021-09-21 6:32 Miroslav Šulc
2021-09-19 1:18 Sam James
2021-08-27 10:50 Lars Wendler
2021-08-24 13:17 Thomas Deutschmann
2021-06-30 20:40 Lars Wendler
2021-06-30 20:16 Lars Wendler
2021-06-04 7:33 Thomas Deutschmann
2021-05-21 23:05 Thomas Deutschmann
2021-04-24 21:15 Thomas Deutschmann
2019-10-21 23:38 Andreas Sturmlechner
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=1686970100.868c215ffeb611c667c3464fabd24c5ac59fff32.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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