From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [WIP] Hedgewars: update to 1.0.0
Date: Fri, 11 Oct 2019 10:49:19 +0200 [thread overview]
Message-ID: <20191011084919.NnxJVzh4R9y7-rFtK-iAJYK15poeONvxolmL5mtQT0A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15327@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
There is an updated pull request by Anachron against master on the void-packages repository
https://github.com/Anachron/void-packages hedgewars-1.0.0
https://github.com/void-linux/void-packages/pull/15327
[WIP] Hedgewars: update to 1.0.0
A patch file from https://github.com/void-linux/void-packages/pull/15327.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hedgewars-1.0.0-15327.patch --]
[-- Type: text/x-diff, Size: 1355 bytes --]
From 778571829f387ace95b6d20dd0a36cfdc474d551 Mon Sep 17 00:00:00 2001
From: Anachron <gith@cron.world>
Date: Fri, 11 Oct 2019 10:47:32 +0200
Subject: [PATCH] Hedgewars: update to 1.0.0
---
srcpkgs/hedgewars/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/hedgewars/template b/srcpkgs/hedgewars/template
index acf0a0f9141..967083f54ef 100644
--- a/srcpkgs/hedgewars/template
+++ b/srcpkgs/hedgewars/template
@@ -1,6 +1,6 @@
# Template file for 'hedgewars'
pkgname=hedgewars
-version=0.9.25
+version=1.0.0
revision=1
wrksrc="${pkgname}-src-${version}"
build_style=cmake
@@ -15,7 +15,7 @@ maintainer="Jakub Skrzypnik <jot.skrzyp@gmail.com>"
license="GPL-2.0-only"
homepage="https://www.hedgewars.org/"
distfiles="https://hedgewars.org/download/releases/hedgewars-src-${version}.tar.bz2"
-checksum=07dc527dbc90dddea894f518aadd67aa2eebb19738739a7c1bd7fd1e608e1c6e
+checksum=211634e61f2e4beecc3c98c6f749601fcd08321fda1ba969b3b3832a004f155b
nopie_files="/usr/bin/hwengine"
nocross="Needs investigation: fails to link hwengine"
@@ -25,6 +25,7 @@ fi
case $XBPS_TARGET_MACHINE in
# forces usage of C engine and ghc due to a 32 bit freepascal bug
+ # https://travis-ci.org/void-linux/void-packages/jobs/596458977#L4316
i686*)
hostmakedepends+=" glew-devel ghc"
nopie_files+=" /usr/bin/hedgewars"
next prev parent reply other threads:[~2019-10-11 8:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 6:42 [PR PATCH] " voidlinux-github
2019-10-11 8:49 ` voidlinux-github [this message]
2019-10-11 8:49 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-11 9:32 ` voidlinux-github
2019-10-11 9:41 ` voidlinux-github
2019-10-11 9:50 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-11 9:50 ` voidlinux-github
2019-10-11 9:51 ` voidlinux-github
2019-10-11 10:03 ` voidlinux-github
2019-10-12 8:52 ` voidlinux-github
2019-10-12 9:14 ` voidlinux-github
2019-10-13 12:28 ` voidlinux-github
2019-10-13 12:30 ` voidlinux-github
2019-10-15 19:40 ` voidlinux-github
2019-10-15 22:15 ` voidlinux-github
2019-10-16 9:55 ` voidlinux-github
2019-10-18 17:08 ` voidlinux-github
2019-10-28 14:51 ` [PR PATCH] [Closed]: " voidlinux-github
2019-10-28 14:51 ` 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=20191011084919.NnxJVzh4R9y7-rFtK-iAJYK15poeONvxolmL5mtQT0A@z \
--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).