From: MattTreadwell <MattTreadwell@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: minecraft-launcher-2.1.13829
Date: Fri, 15 May 2020 03:48:07 +0200 [thread overview]
Message-ID: <20200515014807.u_XVpv7lp_arnvWfwZfOoYAKNJxt3taUbqVtDWqPack@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: 757 bytes --]
New comment by MattTreadwell on void-packages repository
https://github.com/void-linux/void-packages/pull/21940#issuecomment-628977750
Comment:
@the-maldridge I'm not really sure why it's necessary to debate the purpose of this package when it was basically given the ok a few months ago https://github.com/void-linux/void-packages/pull/14268#pullrequestreview-290136949. I don't see the harm in giving users a choice between MultiMC and the official launcher. Why not have the freedom of choice?
If JARs should be user-manged, the existing `minecraft` package should be removed. Although, it kind of defeats the purpose of having a package manager.
What do think is the ideal way to solve https://github.com/void-linux/void-packages/issues/13139?
next prev parent reply other threads:[~2020-05-15 1:48 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
2020-05-14 23:07 ` the-maldridge
2020-05-14 23:07 ` [PR PATCH] [Closed]: " the-maldridge
2020-05-15 1:48 ` MattTreadwell [this message]
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=20200515014807.u_XVpv7lp_arnvWfwZfOoYAKNJxt3taUbqVtDWqPack@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).