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.2.0.
Date: Mon, 18 Apr 2022 13:53:16 +0200	[thread overview]
Message-ID: <20220418115316.34Gs7X9iq0M-O9c_1Hz0TNpoNorYRAedjnAEcC4YjU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36749@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1231 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/36749

PolyMC: update to 1.2.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/36749.patch is attached

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

From a3024362606ab4b412c6e5d0fbc2705c03841942 Mon Sep 17 00:00:00 2001
From: Philipp David <pd@3b.pm>
Date: Mon, 18 Apr 2022 13:30:56 +0200
Subject: [PATCH] PolyMC: update to 1.2.0.

---
 srcpkgs/PolyMC/template | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/PolyMC/template b/srcpkgs/PolyMC/template
index 3b3b0deb3466..87f8218f413a 100644
--- a/srcpkgs/PolyMC/template
+++ b/srcpkgs/PolyMC/template
@@ -1,9 +1,9 @@
 # Template file for 'PolyMC'
 pkgname=PolyMC
-version=1.1.1
+version=1.2.0
 revision=1
 build_style=cmake
-configure_args="-DLauncher_BUILD_PLATFORM=Void -DLauncher_PORTABLE=0
+configure_args="-DLauncher_BUILD_PLATFORM=Void
  -DLauncher_VERSION_BUILD=${revision}"
 hostmakedepends="openjdk8 qt5-host-tools qt5-qmake"
 makedepends="qt5-devel"
@@ -13,7 +13,11 @@ 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=7ade9abc3a6f61ed27a129c10084c783cc9a3266484a53e29dabcc1cbb0ba5c4
+checksum=f2bc1b0b18a166445e3ca03d3e0f606043c57b1811317079603bef4e44994484
+
+if [ -z "$XBPS_CHECK_PKGS" ]; then
+	configure_args+=" -DBUILD_TESTING=0"
+fi
 
 case "$XBPS_TARGET_MACHINE" in
 	armv*) broken="https://github.com/MultiMC/MultiMC5/issues/2895";;

  parent reply	other threads:[~2022-04-18 11:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 11:34 [PR PATCH] " oynqr
2022-04-18 11:38 ` [PR REVIEW] " DioEgizio
2022-04-18 11:38 ` DioEgizio
2022-04-18 11:53 ` oynqr [this message]
2022-04-18 23:23 ` tibequadorian
2022-04-19  8:08 ` DioEgizio
2022-04-19 19:01 ` paper42
2022-04-20 13:34 ` [PR PATCH] [Updated] " oynqr
2022-04-28 17:56 ` PolyMC: update to 1.2.1 DioEgizio
2022-04-29 10:32 ` [PR PATCH] [Merged]: " paper42

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=20220418115316.34Gs7X9iq0M-O9c_1Hz0TNpoNorYRAedjnAEcC4YjU4@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).