From: MattTreadwell <MattTreadwell@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: minecraft-launcher-2.1.13829
Date: Thu, 14 May 2020 21:57:18 +0200 [thread overview]
Message-ID: <20200514195718.B5tIdWMfoDqLloxWfrWg_6UqZh01hBqaIKkDBKaEx9o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21940@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
New comment by MattTreadwell on void-packages repository
https://github.com/void-linux/void-packages/pull/21940#issuecomment-628855453
Comment:
I don't think there's a good reason to continue to distributing the legacy launcher. When I tried updating the existing minecraft launcher (to the electron one), there was some push back in https://github.com/void-linux/void-packages/issues/13139.
MultiMC seems like it does solve the issue. On the other hand, some users may want to use Mojang's official launcher even though it's closed source. I mean, there's an `oraclejdk` package even though most people are using `openjdk` without issue.
For the legacy package, it should either be purged or at the very least use some of the updates I proposed (whether it's as `minecraft` or `minecraft-legacy`).
next prev parent reply other threads:[~2020-05-14 19:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 1:18 [PR PATCH] " MattTreadwell
2020-05-14 1:27 ` [PR PATCH] [Updated] " MattTreadwell
2020-05-14 1:30 ` MattTreadwell
2020-05-14 1:33 ` MattTreadwell
2020-05-14 1:41 ` MattTreadwell
2020-05-14 2:09 ` MattTreadwell
2020-05-14 3:30 ` MattTreadwell
2020-05-14 3:34 ` MattTreadwell
2020-05-14 4:13 ` Vaelatern
2020-05-14 4:26 ` MattTreadwell
2020-05-14 4:38 ` [PR PATCH] [Updated] " MattTreadwell
2020-05-14 18:12 ` Vaelatern
2020-05-14 19:57 ` MattTreadwell
2020-05-14 19:57 ` MattTreadwell [this message]
2020-05-14 23:07 ` the-maldridge
2020-05-14 23:07 ` [PR PATCH] [Closed]: " the-maldridge
2020-05-15 1:48 ` MattTreadwell
2020-05-15 1:55 ` MattTreadwell
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=20200514195718.B5tIdWMfoDqLloxWfrWg_6UqZh01hBqaIKkDBKaEx9o@z \
--to=matttreadwell@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).