From: wpbirney <wpbirney@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] squirrel: update to 3.2
Date: Thu, 14 Apr 2022 03:37:54 +0200 [thread overview]
Message-ID: <20220414013754.IE0p_2V-sQNIy3hPlm2HF2D_PX-snkp_xaCR2egrSV4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36686@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
There is an updated pull request by wpbirney against master on the void-packages repository
https://github.com/wpbirney/void-packages squirrel
https://github.com/void-linux/void-packages/pull/36686
squirrel: update to 3.2
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/36686.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-squirrel-36686.patch --]
[-- Type: text/x-diff, Size: 1195 bytes --]
From e5b6e418a16bb733b91c85d71ebbfb2c7e9c4882 Mon Sep 17 00:00:00 2001
From: blackbeard420 <blackbeard@blackbeard420.me>
Date: Wed, 13 Apr 2022 21:32:11 -0400
Subject: [PATCH] squirrel: update to 3.2
---
srcpkgs/squirrel/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/squirrel/template b/srcpkgs/squirrel/template
index f8254ef94403..7b05ec621cfa 100644
--- a/srcpkgs/squirrel/template
+++ b/srcpkgs/squirrel/template
@@ -1,15 +1,15 @@
# Template file for 'squirrel'
pkgname=squirrel
-version=3.1
+version=3.2
revision=1
build_style=cmake
-short_desc="The Squirrel Programming Language"
+depends="${pkgname}-libs>=${version}_${revision}"
+short_desc="Squirrel Programming Language"
maintainer="Wilson Birney <wpb@360scada.com>"
license="MIT"
homepage="http://www.squirrel-lang.org/"
distfiles="https://github.com/albertodemichelis/squirrel/archive/v${version}.tar.gz>${pkgname}-${version}.tar.gz"
-checksum=51942b8638a97b673e34ecf3ca50304996fa99bbdbfa7fe93d9744e6769b2f95
-depends="${pkgname}-libs>=${version}_${revision}"
+checksum=02805414cfadd5bbb921891d3599b83375a40650abd6404a8ab407dc5e86a996
post_install() {
vlicense COPYRIGHT
next prev parent reply other threads:[~2022-04-14 1:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 1:35 [PR PATCH] " wpbirney
2022-04-14 1:37 ` wpbirney [this message]
2022-06-29 20:28 ` [PR PATCH] [Closed]: " Duncaen
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=20220414013754.IE0p_2V-sQNIy3hPlm2HF2D_PX-snkp_xaCR2egrSV4@z \
--to=wpbirney@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).