Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] praat: update to 6.2.09
Date: Sun, 13 Mar 2022 20:29:54 +0100	[thread overview]
Message-ID: <20220313192954.5tzq6eZOyPU-PzKtPc8g2g5qfVRwTNbD92frlp2FI_c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35293@inbox.vuxu.org>

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

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

https://github.com/newbluemoon/void-packages praat
https://github.com/void-linux/void-packages/pull/35293

praat: update to 6.2.09
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!-- 
#### Local build testing
- 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/35293.patch is attached

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

From 7d34f2cd7e4ffa837afbc0e2cb9fb0e35ac03ca1 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Sat, 29 Jan 2022 14:37:43 +0100
Subject: [PATCH] praat: update to 6.2.09

---
 srcpkgs/praat/template | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/praat/template b/srcpkgs/praat/template
index b64c721ab717..ac2777a445cc 100644
--- a/srcpkgs/praat/template
+++ b/srcpkgs/praat/template
@@ -1,6 +1,6 @@
 # Template file for 'praat'
 pkgname=praat
-version=6.2.04
+version=6.2.09
 revision=1
 create_wrksrc=yes
 hostmakedepends="pkg-config"
@@ -12,7 +12,7 @@ license="GPL-2.0-or-later"
 homepage="http://www.praat.org/"
 changelog="http://www.fon.hum.uva.nl/praat/manual/What_s_new_.html"
 distfiles="https://github.com/praat/praat/archive/v${version}.tar.gz"
-checksum=65c8a70d02760fdf36e04d892412441d8d338867db30d593aea1c202aa937c24
+checksum=3c38b8af267b152a3fda1af78fe8cc26a1717f70a886387e657c55746f666af1
 
 # there are a number of pre-defined Makefiles for certain configurations
 # build options are used to choose which one to use among a selected few
@@ -34,13 +34,11 @@ do_build() {
 
 		cp makefiles/makefile.defs.linux.${_variant} ./makefile.defs
 		sed -i -e 's/$(LIBS)/& $(LDFLAGS)/' Makefile
-		sed -i -e 's/CC = gcc/CC = "${CC}"/' \
-		 -e 's/CXX = g++/CXX = "${CXX}"/' \
-		 -e 's/LINK = g++/LINK = "${CXX}"/' \
-		 -e 's/AR = ar/AR = "${AR}"/' \
+		sed -i -e 's/AR = ar/AR = "${AR}"/' \
 		 -e 's/-O\(1\|3\)//' \
 		 -e 's/CFLAGS =/CFLAGS +=/' \
 		 -e 's/CXXFLAGS =/CXXFLAGS +=/' \
+		 -e 's/-no-pie//' \
 		 makefile.defs
 
 		if [ $XBPS_TARGET_ENDIAN == "le" ]; then

  parent reply	other threads:[~2022-03-13 19:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 13:41 [PR PATCH] praat: update to 6.2.07 newbluemoon
2022-02-06 23:16 ` [PR REVIEW] " ericonr
2022-02-07 18:42 ` newbluemoon
2022-02-19 17:55 ` [PR PATCH] [Updated] " newbluemoon
2022-02-19 17:59 ` [PR REVIEW] praat: update to 6.2.09 newbluemoon
2022-02-25 18:41 ` [PR PATCH] [Updated] " newbluemoon
2022-03-13 19:29 ` newbluemoon [this message]
2022-03-13 21:19 ` [PR PATCH] [Merged]: " paper42

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=20220313192954.5tzq6eZOyPU-PzKtPc8g2g5qfVRwTNbD92frlp2FI_c@z \
    --to=newbluemoon@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).