From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] crystal: update to 0.29.0.
Date: Thu, 06 Jun 2019 14:07:13 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12206@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
There is a new pull request by gcat432 against master on the void-packages repository
https://github.com/gcat432/void-packages crystal-0.29.0
https://github.com/void-linux/void-packages/pull/12206
crystal: update to 0.29.0.
A patch file from https://github.com/void-linux/void-packages/pull/12206.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-crystal-0.29.0-12206.patch --]
[-- Type: application/text/x-diff, Size: 2156 bytes --]
From b78ca907c9d57f95fb87665de65c65aeae85d677 Mon Sep 17 00:00:00 2001
From: Gangsta Cat <grumpy@keemail.me>
Date: Thu, 6 Jun 2019 03:27:03 +0200
Subject: [PATCH] crystal: update to 0.29.0.
---
srcpkgs/crystal/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/crystal/template b/srcpkgs/crystal/template
index 0a5ad7c09b4..b0c1e00458c 100644
--- a/srcpkgs/crystal/template
+++ b/srcpkgs/crystal/template
@@ -1,9 +1,9 @@
# Template file for 'crystal'
pkgname=crystal
-version=0.28.0
+version=0.29.0
revision=1
_shardsversion=0.8.1
-_bootstrapversion=0.28.0
+_bootstrapversion=0.29.0
_bootstraprevision=1
hostmakedepends="git llvm6.0"
makedepends="gc-devel libatomic_ops pcre-devel libevent-devel libyaml-devel
@@ -18,7 +18,7 @@ homepage="https://crystal-lang.org/"
distfiles="
https://github.com/crystal-lang/crystal/archive/${version}.tar.gz
https://github.com/crystal-lang/shards/archive/v${_shardsversion}.tar.gz"
-checksum="4206f57c6345454504ec4cd8cbd1b9354b9be29fae4cdcdd173f4a28cc13b102
+checksum="c2265b2a904ded282751f59a3bd0367072058eee1cf51ebe0af03a572f8e19b9
75c74ab6acf2d5c59f61a7efd3bbc3c4b1d65217f910340cb818ebf5233207a5"
nocross="FIXME: someone needs to sort out the llvm --cxxflags for cross building"
_crystalflags="--release --no-debug --progress"
@@ -31,11 +31,11 @@ if [ "$build_option_binary_bootstrap" ]; then
case "$XBPS_MACHINE" in
x86_64)
distfiles+=" https://github.com/crystal-lang/crystal/releases/download/${_bootstrapversion}/crystal-${_bootstrapversion}-${_bootstraprevision}-linux-x86_64.tar.gz"
- checksum+=" 0ae13581b0d30740f232c9a29e444184121fc263b22c01d2c94290660860982e"
+ checksum+=" cad27db08542947e788e7c06fc00691c05ba678cedf20ecf9baa8cee741233f3"
;;
i686)
distfiles+=" https://github.com/crystal-lang/crystal/releases/download/${_bootstrapversion}/crystal-${_bootstrapversion}-${_bootstraprevision}-linux-i686.tar.gz"
- checksum+=" a6879503badb064c9420d92f126ab08b0441a2b49d84e4fe238a52214a65ac33"
+ checksum+=" 0296df4824cadddadba0c052bd1fdc4ad1bdfe5758c688e7b1764ca163bca0db"
;;
*)
broken="cannot be built on $XBPS_MACHINE"
next reply other threads:[~2019-06-06 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 12:07 voidlinux-github [this message]
2019-06-06 12:20 ` voidlinux-github
2019-06-06 12:38 ` voidlinux-github
2019-06-06 12:41 ` voidlinux-github
2019-06-06 12:45 ` [PR PATCH] [Merged]: " voidlinux-github
-- strict thread matches above, loose matches on Subject: below --
2019-06-06 1:32 [PR PATCH] " voidlinux-github
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-12206@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).