From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] pipewire: update to 0.3.17
Date: Mon, 30 Nov 2020 16:56:21 +0100 [thread overview]
Message-ID: <20201130155621.hY2Kf-OPKj7p77m1u6kztta1FpXYQRAb4OaTNUswCIw@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: 485 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.17
https://github.com/void-linux/void-packages/pull/26822
pipewire: update to 0.3.17
Basic instructions to have pipewire replace pulseaudio that worked on my system with this version:
https://gist.github.com/st3r4g/6c681a28b0403b3b02636f510ff68039
A patch file from https://github.com/void-linux/void-packages/pull/26822.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pipewire-0.3.17-26822.patch --]
[-- Type: text/x-diff, Size: 1659 bytes --]
From ec6a581b70778403eb8ce96c26b62dc319c4990c Mon Sep 17 00:00:00 2001
From: Stefano Ragni <st3r4g@protonmail.com>
Date: Mon, 30 Nov 2020 10:40:34 +0100
Subject: [PATCH] pipewire: update to 0.3.17
Also move the alsa configs to alsa-pipewire
---
srcpkgs/pipewire/template | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/pipewire/template b/srcpkgs/pipewire/template
index 930e4b6a0af..d3fcaad9622 100644
--- a/srcpkgs/pipewire/template
+++ b/srcpkgs/pipewire/template
@@ -1,6 +1,6 @@
# Template file for 'pipewire'
pkgname=pipewire
-version=0.3.12
+version=0.3.17
revision=1
build_style=meson
configure_args="-Dman=true -Dgstreamer=true -Ddocs=true -Dsystemd=false
@@ -15,7 +15,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=98c71228aad2f8443e73a524106f32ca9a74e13c2bf55b65b1e06b72325892cd
+checksum=46d2f597506ef56b0be54498ab26b58bacdd7cae30f87f47836f1f717a0d05ac
conf_files="/etc/pipewire/pipewire.conf"
if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
@@ -24,6 +24,11 @@ if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
fi
post_install() {
+ # alsa.conf scans /usr/etc/alsa/conf.d
+ mkdir -p ${DESTDIR}/usr/etc/alsa
+ mv ${DESTDIR}/usr/share/alsa/alsa.conf.d ${DESTDIR}/usr/etc/alsa/conf.d
+ rm -d ${DESTDIR}/usr/share/alsa
+
vlicense LICENSE
}
@@ -138,6 +143,7 @@ alsa-pipewire_package() {
short_desc+=" - ALSA client library"
pkg_install() {
vmove usr/lib/alsa-lib
+ vmove usr/etc/alsa/conf.d
}
}
next prev parent reply other threads:[~2020-11-30 15:56 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 ` st3r4g [this message]
2020-11-30 16:01 ` [PR PATCH] [Updated] " 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
2020-11-30 17:09 ` [PR REVIEW] " 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=20201130155621.hY2Kf-OPKj7p77m1u6kztta1FpXYQRAb4OaTNUswCIw@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).