Github messages for voidlinux
 help / color / mirror / Atom feed
From: bugcrazy <bugcrazy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] devilutionX: update to 1.1.0
Date: Sun, 11 Oct 2020 07:26:15 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25511@inbox.vuxu.org> (raw)

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

There is a new pull request by bugcrazy against master on the void-packages repository

https://github.com/bugcrazy/void-packages patch-5
https://github.com/void-linux/void-packages/pull/25511

devilutionX: update to 1.1.0


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

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

From 0445ba54464ea6dd7858de8d7bdf5ae3b00f3eeb Mon Sep 17 00:00:00 2001
From: bugcrazy <39757967+bugcrazy@users.noreply.github.com>
Date: Sun, 11 Oct 2020 02:24:27 -0300
Subject: [PATCH] devilutionX: update to 1.1.0

---
 srcpkgs/devilutionX/template | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/srcpkgs/devilutionX/template b/srcpkgs/devilutionX/template
index 43963071c58..ccfe1770e72 100644
--- a/srcpkgs/devilutionX/template
+++ b/srcpkgs/devilutionX/template
@@ -1,6 +1,6 @@
 # Template file for 'devilutionX'
 pkgname=devilutionX
-version=1.0.1
+version=1.1.0
 revision=1
 build_style=cmake
 configure_args="-DBINARY_RELEASE=ON -DTTF_FONT_PATH=\"/usr/share/fonts/truetype/CharisSILB.ttf\""
@@ -10,7 +10,7 @@ maintainer="MarcoAPC <marcoaureliopc@gmail.com>"
 license="Unlicense"
 homepage="https://github.com/diasurgical/devilutionX"
 distfiles="https://github.com/diasurgical/devilutionX/archive/${version}.tar.gz"
-checksum=165564fefdbfd0b4fbf74688ea1beb1d811eb1d8e200b9faad5b70ae2ac7564e
+checksum=395ec298df5383abe60550d45adba5e5811984589ccb1e504891b267b3c467c1
 
 nocross="https://build.voidlinux.org/builders/aarch64-musl_builder/builds/25453/steps/shell_3/logs/stdio"
 
@@ -18,13 +18,9 @@ do_install() {
 	vbin build/devilutionx
 	vmkdir usr/share/applications
 	vmkdir usr/share/fonts/truetype
-	vmkdir usr/share/icons/hicolor/16x16/apps
-	vmkdir usr/share/icons/hicolor/32x32/apps
-	vmkdir usr/share/icons/hicolor/48x48/apps
+	vmkdir usr/share/icons/hicolor/512x512/apps
 	vinstall Packaging/fedora/devilutionx.desktop 0644 usr/share/applications
 	vinstall Packaging/resources/CharisSILB.ttf 0644 usr/share/fonts/truetype
-	cp Packaging/resources/16.png ${DESTDIR}/usr/share/icons/hicolor/16x16/apps/devilutionx.png
-	cp Packaging/resources/Diablo_32.png ${DESTDIR}/usr/share/icons/hicolor/32x32/apps/devilutionx.png
-	cp Packaging/resources/Diablo_48.png ${DESTDIR}/usr/share/icons/hicolor/48x48/apps/devilutionx.png
+	cp Packaging/resources/icon.png ${DESTDIR}/usr/share/icons/hicolor/512x512/apps/devilutionx.png
 	vlicense LICENSE
 }

             reply	other threads:[~2020-10-11  5:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11  5:26 bugcrazy [this message]
2020-10-11  8:25 ` bugcrazy
2021-02-15  4:26 ` [PR PATCH] [Closed]: " ericonr
2021-02-17  4:18 ` bugcrazy
2021-02-17 13:59 ` ericonr
2021-02-18 22:23 ` bugcrazy

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-25511@inbox.vuxu.org \
    --to=bugcrazy@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).