From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] Updates for the Minecraft package?
Date: Mon, 15 Jul 2019 22:10:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13139@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
New issue by Wychmire on void-packages repository
https://github.com/void-linux/void-packages/issues/13139
Description: This is not a package request.
The current minecraft template installs the fifth iteration of the minecraft launcher. Minecraft is up to it's seventh iteration and is considerably different from the fifth, especially in that it uses Electron instead of whatever it used before (java?). You can take a look at the visual difference by looking at this [image of the older launcher](https://gamepedia.cursecdn.com/minecraft_gamepedia/a/a5/Launcher-1.6.png) and [this one of the newer launcher](https://gamepedia.cursecdn.com/minecraft_gamepedia/7/76/2019Launcher.png)
As long as the fifth launcher is available from the URL it uses I feel like it should still be installable since it's electron free and still works great, but maybe that's just me being nostalgic?
I've already written a working template which I've installed and am using. I've pushed it to the [minecraft-launcher branch](https://github.com/Wychmire/void-packages/tree/minecraft-launcher/srcpkgs/minecraft-launcher) in my fork.
So my thinking was either
1. The `minecraft` package sticks around as-is and the new launcher is added as `minecraft-launcher` or,
2. The `minecraft` package is updated to use the new launcher and the old one is **a)** renamed to `minecraft-legacy`, `minecraft-launcher-legacy` or something similar or **b)** deleted.
Thoughts?
next reply other threads:[~2019-07-15 20:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 20:10 voidlinux-github [this message]
2019-09-06 23:03 ` voidlinux-github
2019-09-07 8:21 ` voidlinux-github
2019-09-07 22:08 ` voidlinux-github
2019-09-07 22:10 ` voidlinux-github
2019-09-08 7:09 ` voidlinux-github
2019-09-08 7:09 ` voidlinux-github
2019-09-08 13:33 ` voidlinux-github
2019-09-08 13:33 ` voidlinux-github
2019-09-12 21:38 ` voidlinux-github
2019-09-14 1:46 ` voidlinux-github
2019-09-14 2:01 ` voidlinux-github
2020-07-14 18:52 ` Chocimier
2020-07-14 18:52 ` [ISSUE] [CLOSED] " Chocimier
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-13139@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).