Github messages for voidlinux
 help / color / mirror / Atom feed
From: gavinhoward <gavinhoward@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bc-gh: update to 6.1.1
Date: Wed, 02 Nov 2022 15:02:04 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40303@inbox.vuxu.org> (raw)

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

There is a new pull request by gavinhoward against master on the void-packages repository

https://github.com/gavinhoward/void-packages master
https://github.com/void-linux/void-packages/pull/40303

bc-gh: update to 6.1.1
This also changes the build to use a predefined build setup, which will build a bc that defaults to the behavior of the GNU bc and dc.

Signed-off-by: Gavin Howard <gavin@yzena.com>

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

A patch file from https://github.com/void-linux/void-packages/pull/40303.patch is attached

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

From 0bba73be4446b63e8bcce931ed640af9d107942b Mon Sep 17 00:00:00 2001
From: Gavin Howard <gavin@yzena.com>
Date: Wed, 2 Nov 2022 07:04:28 -0600
Subject: [PATCH] bc-gh: update to 6.1.1

This also changes the build to use a predefined build setup, which will
build a bc that defaults to the behavior of the GNU bc and dc.

Signed-off-by: Gavin Howard <gavin@yzena.com>
---
 srcpkgs/bc-gh/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/bc-gh/template b/srcpkgs/bc-gh/template
index 3ae95d694e9c..57bf62269fcd 100644
--- a/srcpkgs/bc-gh/template
+++ b/srcpkgs/bc-gh/template
@@ -1,6 +1,6 @@
 # Template file for 'bc-gh'
 pkgname=bc-gh
-version=5.2.2
+version=6.1.1
 revision=1
 wrksrc="bc-${version}"
 short_desc="Implementation of POSIX bc with GNU extensions"
@@ -9,7 +9,7 @@ license="BSD-2-Clause"
 homepage="https://git.yzena.com/gavin/bc"
 changelog="https://git.yzena.com/gavin/bc/raw/branch/master/NEWS.md"
 distfiles="https://github.com/gavinhoward/bc/releases/download/${version}/bc-${version}.tar.xz"
-checksum=480249fc0e6a54cb2dc0059734ce433bff344d27b40b8591ae410068e1573352
+checksum=b6de9e2fa4fcb1902c1686760dd90217543128f0298d418951ab1e9a03964097
 alternatives="
  bc:bc:/usr/bin/bc-gh
  bc:bc.1:/usr/share/man/man1/bc-gh.1
@@ -21,7 +21,7 @@ alternatives="
 do_configure() {
 	PREFIX=/usr DESTDIR="${DESTDIR}" EXECSUFFIX=-gh CC="${CC}" CFLAGS="${CFLAGS}" \
 	HOSTCC="${CC_FOR_BUILD}" HOSTCFLAGS="${CFLAGS_FOR_BUILD}" ./configure.sh -GM \
-	-sbc.banner -sdc.tty_mode
+	-pGNU
 }
 do_build() {
 	make ${makejobs}

             reply	other threads:[~2022-11-02 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 14:02 gavinhoward [this message]
2023-02-01  2:07 ` github-actions
2023-02-01  2:57 ` [PR PATCH] [Closed]: " gavinhoward
2023-02-01  2:57 ` [PR PATCH] [Updated] " gavinhoward

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40303@inbox.vuxu.org \
    --to=gavinhoward@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).