Github messages for voidlinux
 help / color / mirror / Atom feed
From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] bluez-alsa: update to 3.1.0
Date: Wed, 23 Jun 2021 14:48:44 +0200	[thread overview]
Message-ID: <20210623124844.GWCTIwiryxH1e0bfmc6LT8Y39uRqQcrv0B8czWV7YXs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31603@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]

There is an updated pull request by amak79 against master on the void-packages repository

https://github.com/amak79/void-packages bluez-alsa
https://github.com/void-linux/void-packages/pull/31603

bluez-alsa: update to 3.1.0
<!-- 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

<!--
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/31603.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bluez-alsa-31603.patch --]
[-- Type: text/x-diff, Size: 1973 bytes --]

From 28421f43e104ca5950e6e1444961cf563d62d4ab Mon Sep 17 00:00:00 2001
From: amak <amak.git@outlook.com>
Date: Tue, 22 Jun 2021 13:19:13 +1000
Subject: [PATCH] bluez-alsa: update to 3.1.0

---
 srcpkgs/bluez-alsa/template | 25 +++++++++----------------
 1 file changed, 9 insertions(+), 16 deletions(-)

diff --git a/srcpkgs/bluez-alsa/template b/srcpkgs/bluez-alsa/template
index d01ec201aa12..b01f8fe180d0 100644
--- a/srcpkgs/bluez-alsa/template
+++ b/srcpkgs/bluez-alsa/template
@@ -1,32 +1,25 @@
 # Template file for 'bluez-alsa'
 pkgname=bluez-alsa
-version=3.0.0
-revision=3
+version=3.1.0
+revision=1
 build_style=gnu-configure
-configure_args="--enable-aac --disable-hcitop --disable-debug
- $(vopt_if man --enable-manpages)"
-hostmakedepends="pkg-config automake libtool $(vopt_if man pandoc)"
-makedepends="alsa-lib-devel fdk-aac-devel libbluetooth-devel libglib-devel
- ortp-devel sbc-devel"
+configure_args="--enable-aac --enable-aptx --with-libopenaptx --enable-ldac
+ --enable-manpages --disable-debug --disable-hcitop"
+hostmakedepends="pkg-config automake libtool python3-docutils"
+makedepends="alsa-lib-devel fdk-aac-devel ldacBT-devel libbluetooth-devel
+ libglib-devel libopenaptx-devel ortp-devel sbc-devel"
 short_desc="Bluetooth Audio ALSA Backend"
 maintainer="Toyam Cox <Vaelatern@voidlinux.org>"
 license="MIT"
 homepage="https://github.com/Arkq/bluez-alsa"
+changelog="https://raw.githubusercontent.com/Arkq/bluez-alsa/master/NEWS"
 distfiles="https://github.com/Arkq/bluez-alsa/archive/v${version}.tar.gz"
-checksum=8b9bc36be922c10c6628ddf84b13dfadfeb3ab0bcf72bad842c66f3120abc6b2
+checksum=d9a878d9fd7f18842c9c8ed83bc96cab684753c90f2751d575a3cdd776ec78a5
 system_accounts="_bluez_alsa"
 _bluez_alsa_groups="audio"
 
 CFLAGS="-fcommon"
 
-build_options="man"
-desc_option_man="Use pandoc to build manpages"
-
-case "$XBPS_MACHINE" in
-	x86_64*|i686|ppc64le*) build_options_default="man";;
-	*) ;;
-esac
-
 pre_configure() {
 	autoreconf -fi
 }

  parent reply	other threads:[~2021-06-23 12:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  3:32 [PR PATCH] " amak79
2021-06-23 12:24 ` ericonr
2021-06-23 12:48 ` amak79 [this message]
2021-06-23 12:52 ` amak79
2021-06-23 16:50 ` [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=20210623124844.GWCTIwiryxH1e0bfmc6LT8Y39uRqQcrv0B8czWV7YXs@z \
    --to=amak79@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).