Github messages for voidlinux
 help / color / mirror / Atom feed
From: Toasterbirb <Toasterbirb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] PolyMC package
Date: Mon, 10 Jan 2022 12:30:05 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34978@inbox.vuxu.org> (raw)

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

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

https://github.com/Toasterbirb/void-packages polymc
https://github.com/void-linux/void-packages/pull/34978

PolyMC package
<!-- 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**

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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)


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

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

From c58a2aceb522d11e0afec2bfbf55b9857d909e76 Mon Sep 17 00:00:00 2001
From: Toasterbirb <git@toasterbirb.com>
Date: Mon, 10 Jan 2022 13:25:43 +0200
Subject: [PATCH] PolyMC package

---
 srcpkgs/PolyMC/template | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 srcpkgs/PolyMC/template

diff --git a/srcpkgs/PolyMC/template b/srcpkgs/PolyMC/template
new file mode 100644
index 000000000000..4790a4d81605
--- /dev/null
+++ b/srcpkgs/PolyMC/template
@@ -0,0 +1,33 @@
+# Template file for 'PolyMC'
+pkgname=PolyMC
+version=1.0.4
+revision=2
+wrksrc="PolyMC-${version}"
+hostmakedepends="cmake gcc git"
+makedepends="qt5-devel qtchooser qt5-qmake zlib-devel openjdk libglib-devel"
+short_desc="Minecraft launcher for managing multiple installations at once"
+maintainer="Toasterbirb <git@toasterbirb.com>"
+license="GPL-3.0-or-later"
+homepage="https://github.com/PolyMC/PolyMC"
+
+export Qt5Core_DIR="/usr/lib/cmake/Qt5Core"
+
+do_fetch() {
+	git clone --recursive https://github.com/PolyMC/PolyMC.git ${wrksrc}
+	cd ${wrksrc}
+	git checkout 1.0.4
+}
+
+do_build() {
+	mkdir ${wrksrc}/build
+	cd ${wrksrc}/build
+	cmake -S .. \
+		-DCMAKE_BUILD_TYPE=Release \
+		-DCMAKE_INSTALL_PREFIX="/usr" \
+		-DLauncher_LAYOUT=lin-system
+}
+
+do_install() {
+	cd ${wrksrc}/build
+	make -j$(nproc) PREFIX=/usr DESTDIR=$DESTDIR install
+}

             reply	other threads:[~2022-01-10 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 11:30 Toasterbirb [this message]
2022-01-10 12:23 ` New package: PolyMC Toasterbirb
2022-01-10 12:23 ` [PR PATCH] [Closed]: " Toasterbirb

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