Github messages for voidlinux
 help / color / mirror / Atom feed
From: jason1987d <jason1987d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] stepmania: update to 5.1.0-b2
Date: Thu, 23 Jul 2020 18:02:01 +0200	[thread overview]
Message-ID: <20200723160201.QKLbvAyRMuUWHmgMZsgXlbOJWcy5YVLyCzJINQ-3XvY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23747@inbox.vuxu.org>

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

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

https://github.com/jason1987d/void-packages stepmania-5.1.0-b2
https://github.com/void-linux/void-packages/pull/23747

stepmania: update to 5.1.0-b2
The current version 5.0.12 results in an error "Fatal: crash from within the crash signal handler" upon running stepmania. From https://github.com/stepmania/stepmania/issues/1606 the suggested workaround is to use the 5.1 branch. The version 5.1-beta2 is technically a release that has been available for a long time. There are also 5.3 alpha releases, but this 5.1 I have tested to run.

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-stepmania-5.1.0-b2-23747.patch --]
[-- Type: text/x-diff, Size: 2348 bytes --]

From 7055743e8a8ba8176f55e1336c030140d96c513d Mon Sep 17 00:00:00 2001
From: Jason Manley <jason@jasondavid.tv>
Date: Wed, 22 Jul 2020 14:41:10 -0500
Subject: [PATCH] stepmania: update to 5.1.0-b2.

---
 srcpkgs/stepmania/template | 36 +++++++++++++++++++++---------------
 1 file changed, 21 insertions(+), 15 deletions(-)

diff --git a/srcpkgs/stepmania/template b/srcpkgs/stepmania/template
index 9ec2c4c2421..bd72e8668e2 100644
--- a/srcpkgs/stepmania/template
+++ b/srcpkgs/stepmania/template
@@ -1,28 +1,34 @@
 # Template file for 'stepmania'
 pkgname=stepmania
-version=5.0.12
-revision=2
+version=5.1.0.b2
+revision=1
+# compilation errors with musl
+archs="i686 x86_64"
+wrksrc=${pkgname}-${version%.*}-${version##*.}
 build_style=cmake
 cmake_builddir="Build"
-hostmakedepends="nasm yasm pkg-config git"
+hostmakedepends="yasm pkg-config git"
 makedepends="libmad-devel libvorbis-devel pcre-devel libjpeg-turbo-devel
-alsa-lib-devel libXrandr-devel libva-devel glew-devel"
+ alsa-lib-devel libXrandr-devel libva-devel glew-devel pulseaudio-devel"
 short_desc="Advanced rhythm game"
-maintainer="Michael Aldridge <maldridge@voidlinux.org>"
+maintainer="Jason Manley <jason@jasondavid.tv>"
 license="MIT"
 homepage="http://www.stepmania.com/"
-distfiles="https://github.com/stepmania/stepmania/archive/v${version}.tar.gz"
-checksum=df79bcadd69d4ed60cf560d45386ec275181343495ffd744c3ff8f73c83d4755
+distfiles="https://github.com/stepmania/stepmania/archive/v${version%.*}-${version##*.}.tar.gz"
+checksum=2e311df9b661ba287b046ce377eb0b41e426b73e169841df99fc9fe2baa89310
 
-# Upstream has stated that only x86 hardware can meed the performance
-# constraints and that musl is not supported due to interop issues
-# with Windows
-archs="i686 x86_64"
+post_patch() {
+	vsed -i 's/PULSE_FOUND/PULSEAUDIO_FOUND/g' ${wrksrc}/StepmaniaCore.cmake
+}
 
 post_install() {
+	for i in 16 22 24 32 36 48 64 72 96 128 192 256
+	do
+		vinstall icons/hicolor/${i}x${i}/apps/stepmania-ssc.png 644 \
+			usr/share/icons/hicolor/${i}x${i}/apps stepmania-ssc.png
+	done
+	vinstall stepmania.desktop 644 usr/share/applications stepmania.desktop
 	vlicense Docs/Licenses.txt
-
-	mkdir -p ${DESTDIR}/usr/bin
-	cd ${DESTDIR}
-	ln -sf ../../opt/stepmania-5.0/stepmania usr/bin/
+	vmkdir -p usr/bin
+	ln -sf ../../opt/${pkgname}-${version%.*.*}/stepmania usr/bin/
 }

  parent reply	other threads:[~2020-07-23 16:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 19:46 [PR PATCH] " jason1987d
2020-07-22 19:59 ` [PR REVIEW] " ericonr
2020-07-22 19:59 ` ericonr
2020-07-22 19:59 ` ericonr
2020-07-22 19:59 ` ericonr
2020-07-22 19:59 ` ericonr
2020-07-22 20:06 ` ericonr
2020-07-22 20:06 ` ericonr
2020-07-22 20:08 ` ericonr
2020-07-22 20:18 ` ericonr
2020-07-22 20:21 ` ericonr
2020-07-23  2:31 ` [PR PATCH] [Updated] " jason1987d
2020-07-23  2:32 ` jason1987d
2020-07-23  2:34 ` jason1987d
2020-07-23  3:24 ` [PR PATCH] [Updated] " jason1987d
2020-07-23  3:32 ` jason1987d
2020-07-23  3:48 ` jason1987d
2020-07-23  4:13 ` [PR PATCH] [Updated] " jason1987d
2020-07-23  5:07 ` ericonr
2020-07-23 14:24 ` [PR PATCH] [Updated] " jason1987d
2020-07-23 14:25 ` jason1987d
2020-07-23 14:28 ` ericonr
2020-07-23 15:53 ` jason1987d
2020-07-23 16:02 ` jason1987d [this message]
2020-07-23 16:13 ` [PR REVIEW] " ericonr
2020-07-23 16:20 ` [PR PATCH] [Updated] " jason1987d
2020-07-23 16:54 ` [PR REVIEW] " jason1987d
2020-07-23 18:05 ` jason1987d
2020-07-23 19:46 ` [PR PATCH] [Updated] " jason1987d
2020-07-23 19:46 ` jason1987d
2020-07-23 20:21 ` jason1987d
2020-11-09  4:18 ` jason1987d
2020-11-09  4:18 ` jason1987d
2020-11-09 13:10 ` ericonr
2020-11-21 18:24 ` [PR PATCH] [Closed]: " jason1987d

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=20200723160201.QKLbvAyRMuUWHmgMZsgXlbOJWcy5YVLyCzJINQ-3XvY@z \
    --to=jason1987d@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).