Github messages for voidlinux
 help / color / mirror / Atom feed
From: oynqr <oynqr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] PolyMC: update to 1.4.0.
Date: Sat, 23 Jul 2022 16:40:53 +0200	[thread overview]
Message-ID: <20220723144053.alRapreTTW-r6QJ2COPQ93m-Ar4kON1t__FHKVO8qIA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38211@inbox.vuxu.org>

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

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

https://github.com/oynqr/void-packages PolyMC
https://github.com/void-linux/void-packages/pull/38211

PolyMC: update to 1.4.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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/38211.patch is attached

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

From a0d0a92e96e2fa6b5d699c111c0e9f617af1d5bc Mon Sep 17 00:00:00 2001
From: Philipp David <pd@3b.pm>
Date: Sat, 23 Jul 2022 15:44:25 +0200
Subject: [PATCH] PolyMC: update to 1.4.0.

---
 srcpkgs/PolyMC/template | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/PolyMC/template b/srcpkgs/PolyMC/template
index 3e02c8c9f0d9..08d8da9b7192 100644
--- a/srcpkgs/PolyMC/template
+++ b/srcpkgs/PolyMC/template
@@ -1,11 +1,12 @@
 # Template file for 'PolyMC'
 pkgname=PolyMC
-version=1.3.2
-revision=2
+version=1.4.0
+revision=1
 build_style=cmake
 configure_args="-DLauncher_BUILD_PLATFORM=Void
  -DLauncher_VERSION_BUILD=${revision}"
-hostmakedepends="openjdk8 qt5-host-tools qt5-qmake"
+hostmakedepends="extra-cmake-modules openjdk8 pkg-config qt5-host-tools
+ qt5-qmake scdoc"
 makedepends="qt5-devel"
 depends="virtual?java-runtime qt5-svg qt5-imageformats xrandr"
 short_desc="Custom launcher for Minecraft"
@@ -13,7 +14,7 @@ maintainer="Philipp David <pd@3b.pm>"
 license="GPL-3.0-only"
 homepage="https://polymc.org/"
 distfiles="https://github.com/PolyMC/PolyMC/releases/download/${version}/PolyMC-${version}.tar.gz"
-checksum=c33484ae20c912d3dde2e55f64f24d8b86a9a9547631cd3b10481ddbf90f4735
+checksum=91b67bd4415f288399f824d9dc83a537d69e66f7ace93de4f62c3dd531a729a9
 
 if [ -z "$XBPS_CHECK_PKGS" ]; then
 	configure_args+=" -DBUILD_TESTING=0"
@@ -25,7 +26,7 @@ esac
 
 post_patch() {
 	vsed -i buildconfig/BuildConfig.cpp.in \
-		-e 's/"-" + QString/"_" + QString/'
+		-e 's/+build\./_/'
 	rm -rf .git
 }
 

  reply	other threads:[~2022-07-23 14:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 14:24 [PR PATCH] " oynqr
2022-07-23 14:40 ` oynqr [this message]
2022-07-23 15:10 ` oynqr
2022-07-28 18:39 ` DioEgizio
2022-07-28 18:39 ` DioEgizio
2022-07-29  8:19 ` [PR PATCH] [Updated] " oynqr
2022-07-31  9:07 ` [PR PATCH] [Merged]: PolyMC: update to 1.4.1 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=20220723144053.alRapreTTW-r6QJ2COPQ93m-Ar4kON1t__FHKVO8qIA@z \
    --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).