From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pipewire: update to 0.3.24
Date: Fri, 19 Mar 2021 11:06:39 +0100 [thread overview]
Message-ID: <20210319100639.RY-Rav68qqIBB2HKyp3IpK7AWw6FvB1uuQSSoGgY3Vs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29566@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
There is an updated pull request by st3r4g against master on the void-packages repository
https://github.com/st3r4g/void-packages pipewire-0.3.24
https://github.com/void-linux/void-packages/pull/29566
pipewire: update to 0.3.24
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
Not yet runtime tested.
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/29566.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire-0.3.24-29566.patch --]
[-- Type: text/x-diff, Size: 3790 bytes --]
From 871e93038475b6e9521f69f0c861ab736db47e6f Mon Sep 17 00:00:00 2001
From: Stefano Ragni <stefano.ragni@outlook.com>
Date: Thu, 18 Mar 2021 18:00:45 +0100
Subject: [PATCH] pipewire: update to 0.3.24
---
srcpkgs/pipewire/files/README.voidlinux | 7 +++++++
.../pipewire/patches/autostart-media-session.patch | 14 +++++++++-----
srcpkgs/pipewire/template | 10 +++++-----
3 files changed, 21 insertions(+), 10 deletions(-)
create mode 100644 srcpkgs/pipewire/files/README.voidlinux
diff --git a/srcpkgs/pipewire/files/README.voidlinux b/srcpkgs/pipewire/files/README.voidlinux
new file mode 100644
index 000000000000..7bcb761273b0
--- /dev/null
+++ b/srcpkgs/pipewire/files/README.voidlinux
@@ -0,0 +1,7 @@
+Optional dependencies:
+
+* `alsa-pipewire` for alsa client support
+* `gstreamer1-pipewire` for the gstreamer plugin
+* `libjack-pipewire` for jack replacement
+* `libspa-bluetooth` for bluetooth support
+* `libspa-jack` for running pipewire and jack side-by-side
diff --git a/srcpkgs/pipewire/patches/autostart-media-session.patch b/srcpkgs/pipewire/patches/autostart-media-session.patch
index 2051a868d463..9e2b92b9a665 100644
--- a/srcpkgs/pipewire/patches/autostart-media-session.patch
+++ b/srcpkgs/pipewire/patches/autostart-media-session.patch
@@ -1,11 +1,15 @@
---- src/daemon/pipewire.conf.in.orig 2021-03-04 16:54:52.950015583 +0100
-+++ src/daemon/pipewire.conf.in 2021-03-04 16:55:13.766016281 +0100
-@@ -203,7 +203,7 @@
+Upstream's config does not autostart pipewire-media-session anymore, which
+is an essential component. It's not easy to start it externally in a script
+since it needs the pipewire socket up, and Void doesn't have a mechanism to
+ensure it (systemd socket activation).
+--- src/daemon/pipewire.conf.in.orig 2021-03-18 17:45:02.025992827 +0100
++++ src/daemon/pipewire.conf.in 2021-03-18 17:47:17.606999440 +0100
+@@ -204,7 +204,7 @@
# but it is better to start it as a systemd service.
# Run the session manager with -h for options.
#
-- @comment@"@media_session_path@" = { args = "" }
-+ "@media_session_path@" = { args = "" }
+- @comment@{ path = "@media_session_path@" args = "" }
++ { path = "@media_session_path@" args = "" }
#
# You can optionally start the pulseaudio-server here as well
# but it is better to start it as a systemd service.
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 7a7a6199a1be..5e5edcdc15a5 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,11 +1,11 @@
# Template file for 'pipewire'
pkgname=pipewire
-version=0.3.23
+version=0.3.24
revision=1
build_style=meson
-configure_args="-Dman=true -Dgstreamer=true -Ddocs=true -Dsystemd=false
- -Dbluez5=true -Dffmpeg=true -Dpipewire-alsa=true -Dpipewire-jack=true
- -Dvulkan=true -Dudevrulesdir=/usr/lib/udev/rules.d"
+configure_args="-Dman=enabled -Dgstreamer=enabled -Ddocs=enabled -Dsystemd=disabled
+ -Dbluez5=enabled -Dffmpeg=enabled -Dpipewire-alsa=enabled -Dpipewire-jack=enabled
+ -Dvulkan=enabled -Dudevrulesdir=/usr/lib/udev/rules.d"
hostmakedepends="doxygen graphviz pkg-config xmltoman gettext"
# LDAC support can be enabled when ldacbt is packaged
makedepends="SDL2-devel ffmpeg-devel gst-plugins-base1-devel jack-devel
@@ -18,7 +18,7 @@ license="MIT"
homepage="https://pipewire.org/"
changelog="https://gitlab.freedesktop.org/pipewire/pipewire/-/raw/master/NEWS"
distfiles="https://gitlab.freedesktop.org/pipewire/pipewire/-/archive/${version}/pipewire-${version}.tar.gz"
-checksum=e9a9030032ba8f3b6f9e300dbf755ab439340cd4cbeb3e1bba6f1a18d2c9da92
+checksum=aeca2b44660c4f36eed29cc9c6ccb093ea2778fd0e4ed7665cdfc40b2a49873f
conf_files="/etc/pipewire/pipewire.conf"
replaces="libpulseaudio-pipewire>=0"
next prev parent reply other threads:[~2021-03-19 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 17:02 [PR PATCH] " st3r4g
2021-03-18 17:18 ` st3r4g
2021-03-18 19:14 ` ericonr
2021-03-19 10:06 ` st3r4g [this message]
2021-03-19 10:07 ` st3r4g
2021-03-19 10:10 ` [PR PATCH] [Updated] " st3r4g
2021-03-19 14:06 ` [PR PATCH] [Merged]: " ericonr
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=20210319100639.RY-Rav68qqIBB2HKyp3IpK7AWw6FvB1uuQSSoGgY3Vs@z \
--to=st3r4g@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).