From: Clyybber <Clyybber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] qjackctl: Add build option for jack-session support
Date: Mon, 11 Jan 2021 20:06:25 +0100 [thread overview]
Message-ID: <20210111190625.kmsqw79fxvl-zcMjyS_uSsKGpntULQnDXWqxhGbDB2I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27828@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
There is an updated pull request by Clyybber against master on the void-packages repository
https://github.com/Clyybber/void-packages qjackctlsessionoption
https://github.com/void-linux/void-packages/pull/27828
qjackctl: Add build option for jack-session support
A patch file from https://github.com/void-linux/void-packages/pull/27828.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-qjackctlsessionoption-27828.patch --]
[-- Type: text/x-diff, Size: 1274 bytes --]
From e79a68d11bc54cec7cc6e8d54a31e270c838b483 Mon Sep 17 00:00:00 2001
From: Clyybber <darkmine956@gmail.com>
Date: Mon, 11 Jan 2021 16:15:59 +0100
Subject: [PATCH] qjackctl: Add build option for jack-session support
---
srcpkgs/qjackctl/template | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/qjackctl/template b/srcpkgs/qjackctl/template
index 83743edd237..a7b19841687 100644
--- a/srcpkgs/qjackctl/template
+++ b/srcpkgs/qjackctl/template
@@ -1,7 +1,7 @@
# Template file for 'qjackctl'
pkgname=qjackctl
version=0.9.0
-revision=1
+revision=2
build_style=gnu-configure
build_helper=qmake
hostmakedepends="pkg-config"
@@ -14,6 +14,12 @@ homepage="http://qjackctl.sourceforge.net"
distfiles="${SOURCEFORGE_SITE}/${pkgname}/${pkgname}-${version}.tar.gz"
checksum=5196c5c01b7948c1a8ca37cd3198a7f0fe095a99a34a67086abd3466855b4abd
+build_options="jack_session"
+build_options_default="jack_session"
+desc_option_jack_session="Enable support for the deprecated Jack Session API (which pipewire does not implement)"
+
+configure_args="$(vopt_enable jack_session)"
+
if [ "${CROSS_BUILD}" ]; then
hostmakedepends+=" qt5-host-tools qt5-devel qt5-x11extras-devel"
configure_args+=" ac_cv_path_ac_cv_qmake=${XBPS_WRAPPERDIR}/qmake"
next prev parent reply other threads:[~2021-01-11 19:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 15:17 [PR PATCH] " Clyybber
2021-01-11 18:48 ` [PR REVIEW] " newbluemoon
2021-01-11 18:48 ` newbluemoon
2021-01-11 18:48 ` newbluemoon
2021-01-11 19:06 ` Clyybber [this message]
2021-01-11 19:06 ` Clyybber
2021-01-11 19:13 ` [PR PATCH] [Updated] " Clyybber
2021-01-11 19:16 ` [PR REVIEW] " ericonr
2021-01-11 19:19 ` pullmoll
2021-01-11 19:19 ` [PR PATCH] [Updated] " Clyybber
2021-01-11 19:19 ` [PR REVIEW] " Clyybber
2021-01-11 19:19 ` pullmoll
2021-01-11 19:22 ` Clyybber
2021-01-11 19:22 ` Clyybber
2021-01-11 19:22 ` Clyybber
2021-01-11 19:25 ` Clyybber
2021-01-11 19:34 ` [PR PATCH] [Updated] " Clyybber
2021-01-11 19:35 ` [PR REVIEW] " Clyybber
2021-01-12 3:08 ` [PR PATCH] [Closed]: " ericonr
2021-01-12 3:09 ` 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=20210111190625.kmsqw79fxvl-zcMjyS_uSsKGpntULQnDXWqxhGbDB2I@z \
--to=clyybber@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).