Github messages for voidlinux
 help / color / mirror / Atom feed
From: benalb <benalb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] crispy-doom: update to 5.12.0.
Date: Wed, 07 Sep 2022 14:28:41 +0200	[thread overview]
Message-ID: <20220907122841.ESrnUFGYfv58-baAv1yYiEf4o8FQ7pFZ68ga1MQ7IFk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39052@inbox.vuxu.org>

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

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

https://github.com/benalb/void-packages crispy-doom
https://github.com/void-linux/void-packages/pull/39052

crispy-doom: update to 5.12.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES*
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, (X86-64-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl


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

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

From dc135949b2cab1a67f9d3f80b312d5d0e9877a6d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benjam=C3=ADn=20Albi=C3=B1ana?= <benalb@gmail.com>
Date: Fri, 2 Sep 2022 09:29:33 +0200
Subject: [PATCH] crispy-doom: update to 5.12.0.

---
 srcpkgs/crispy-doom/template | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/crispy-doom/template b/srcpkgs/crispy-doom/template
index acd3fd216a33..6c8ea335d079 100644
--- a/srcpkgs/crispy-doom/template
+++ b/srcpkgs/crispy-doom/template
@@ -1,20 +1,28 @@
 # Template file for 'crispy-doom'
 pkgname=crispy-doom
-version=5.11.1
+version=5.12.0
 revision=1
 wrksrc="crispy-doom-crispy-doom-${version}"
 build_style=gnu-configure
-hostmakedepends="autoconf automake pkg-config"
+hostmakedepends="autoconf automake pkg-config python3"
 makedepends="SDL2-devel SDL2_mixer-devel SDL2_net-devel libsamplerate-devel libpng-devel"
 short_desc="Limit-removing enhanced-resolution Doom source port"
 maintainer="Benjamín Albiñana <benalb@gmail.com>"
 license="GPL-2.0-or-later"
 homepage="https://github.com/fabiangreffrath/crispy-doom"
 distfiles="https://github.com/fabiangreffrath/crispy-doom/archive/crispy-doom-${version}.tar.gz"
-checksum=7c5bb36393dec39b9732e53963dadd6bcc3bd193370c4ec5b1c0121df3b38faa
+checksum=d85d6e76aa949385458b7702e6fb594996745b94032ffb13e1790376eeecb462
 
 CFLAGS="-fcommon"
 
 pre_configure() {
 	autoreconf -fi
 }
+
+post_install() {
+	#Rename default.cfg(5), hexen.cfg(5) and heretic.cfg(5) man pages to avoid conflict
+	#with chocolate-doom
+	mv ${DESTDIR}/usr/share/man/man5/default.cfg.5 ${DESTDIR}/usr/share/man/man5/crispy_default.cfg.5
+	mv ${DESTDIR}/usr/share/man/man5/hexen.cfg.5 ${DESTDIR}/usr/share/man/man5/crispy_hexen.cfg.5
+	mv ${DESTDIR}/usr/share/man/man5/heretic.cfg.5 ${DESTDIR}/usr/share/man/man5/crispy_heretic.cfg.5
+}

  parent reply	other threads:[~2022-09-07 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02  7:31 [PR PATCH] " benalb
2022-09-02  8:53 ` [PR PATCH] [Updated] " benalb
2022-09-07 12:28 ` benalb [this message]
2022-09-07 23:20 ` [PR PATCH] [Merged]: " classabbyamp

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=20220907122841.ESrnUFGYfv58-baAv1yYiEf4o8FQ7pFZ68ga1MQ7IFk@z \
    --to=benalb@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).