From: daerich <daerich@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: MultiMC: remove package(was MultiMC: update to 0.6.14)
Date: Sat, 09 Apr 2022 17:03:11 +0200 [thread overview]
Message-ID: <20220409150311.jkWJdL4VQQucGJemlQClTGFRWDQDgfDG6Sl_D4YiZZI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34495@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
There's a closed pull request on the void-packages repository
MultiMC: remove package(was MultiMC: update to 0.6.14)
https://github.com/void-linux/void-packages/pull/34495
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
Unfortunately upstream changed quite some things on how to reliably acquire this package - partly due to new licensing terms.
Also the way has been paved for installscripts geared towards "popular" distributions(Ubuntu/Fedora). They now only deploy a downloader to embed the package in the users home directory.
__Edit__: It can not be reliably built from source anymore as it is missing the `secrets` library.
~So meld the generic Linux binary with the Ubuntu one recreating the prior Void distribution of this package(Icons and .desktop are part of the Ubuntu package and can't be hosted elsewhere).
This all is necessary due to a certain company from Redmond, WA forcing Minecraft onto their infrastructure.~
<!--
#### 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 [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)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
next prev parent reply other threads:[~2022-04-09 15:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 15:45 [PR PATCH] MultiMC: update to 0.6.14 daerich
2021-12-12 15:52 ` [PR PATCH] [Updated] " daerich
2021-12-12 15:53 ` daerich
2021-12-12 15:57 ` daerich
2021-12-12 16:06 ` daerich
2021-12-12 16:07 ` daerich
2021-12-12 16:57 ` Duncaen
2021-12-12 17:51 ` MultiMC: remove package(was MultiMC: update to 0.6.14) daerich
2021-12-12 17:51 ` daerich
2021-12-12 17:53 ` [PR PATCH] [Updated] " daerich
2021-12-12 17:55 ` daerich
2021-12-19 17:43 ` [PR PATCH] [Updated] " daerich
2021-12-19 17:51 ` daerich
2022-02-10 14:36 ` daerich
2022-04-09 11:30 ` tibequadorian
2022-04-09 15:03 ` daerich [this message]
2022-04-09 15:46 ` tibequadorian
2022-04-09 15:55 ` [PR PATCH] [Updated] " paper42
2022-04-09 16:06 ` [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=20220409150311.jkWJdL4VQQucGJemlQClTGFRWDQDgfDG6Sl_D4YiZZI@z \
--to=daerich@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).