From: oynqr <oynqr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] PrismLauncher: update to 6.1.
Date: Tue, 20 Dec 2022 09:57:04 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41199@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]
There is a new pull request by oynqr against master on the void-packages repository
https://github.com/oynqr/void-packages PrismLauncher
https://github.com/void-linux/void-packages/pull/41199
PrismLauncher: update to 6.1.
<!-- 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, (ARCH-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/41199.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-PrismLauncher-41199.patch --]
[-- Type: text/x-diff, Size: 1123 bytes --]
From faf233b6e091d84809aa1bc90e001744651609fd Mon Sep 17 00:00:00 2001
From: Philipp David <pd@3b.pm>
Date: Tue, 20 Dec 2022 09:36:40 +0100
Subject: [PATCH] PrismLauncher: update to 6.1.
---
srcpkgs/PrismLauncher/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/PrismLauncher/template b/srcpkgs/PrismLauncher/template
index 7c8c167be4b3..65dd77a0807a 100644
--- a/srcpkgs/PrismLauncher/template
+++ b/srcpkgs/PrismLauncher/template
@@ -1,6 +1,6 @@
# Template file for 'PrismLauncher'
pkgname=PrismLauncher
-version=6.0
+version=6.1
revision=1
build_style=cmake
configure_args="-DLauncher_BUILD_PLATFORM=Void"
@@ -13,7 +13,7 @@ maintainer="Philipp David <pd@3b.pm>"
license="GPL-3.0-only"
homepage="https://prismlauncher.org/"
distfiles="https://github.com/PrismLauncher/PrismLauncher/releases/download/${version}/PrismLauncher-${version}.tar.gz"
-checksum=4b8845186e509f62564f47f48b04f8abb3e35523ba8b33c5413475724e49e1dc
+checksum=d89171a982af0f93208b25c33f5f890ca9674bd0573e685da969d6436103da9c
if [ -z "$XBPS_CHECK_PKGS" ]; then
configure_args+=" -DBUILD_TESTING=0"
next reply other threads:[~2022-12-20 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 8:57 oynqr [this message]
2022-12-27 7:03 ` [PR PATCH] [Merged]: " classabbyamp
2022-12-27 7:02 [PR PATCH] " mayhair
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-41199@inbox.vuxu.org \
--to=oynqr@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).