From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] MultiMC mark restricted
Date: Thu, 16 Sep 2021 15:16:06 +0200 [thread overview]
Message-ID: <20210916131606.TmCe4nvIeZQI_NpjbIaWrpi98pi2iTDLqVFvdQEsSpM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32979@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
There is an updated pull request by Duncaen against master on the void-packages repository
https://github.com/Duncaen/void-packages multimc
https://github.com/void-linux/void-packages/pull/32979
MultiMC mark restricted
We are not allowed to use the MultiMC name, artwork or API endpoints for builds from source.
Marking this package as restricted so that we won't ship any binaries for it, users can either download binaries or build the package for personal use.
Also adding it to `removed-packages` so that anyone who has it installed will get it uninstalled instead of being stuck to the version they currently have installed.
https://github.com/void-linux/void-packages/issues/32950
A patch file from https://github.com/void-linux/void-packages/pull/32979.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-multimc-32979.patch --]
[-- Type: text/x-diff, Size: 1151 bytes --]
From 10f8f83f62e50ff8b3cd5193780fd02647fa41b5 Mon Sep 17 00:00:00 2001
From: Duncaen <duncaen@voidlinux.org>
Date: Thu, 16 Sep 2021 14:15:42 +0200
Subject: [PATCH] MultiMC: make package restricted
---
srcpkgs/MultiMC/template | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/MultiMC/template b/srcpkgs/MultiMC/template
index 6f19fc623d0a..2e21f35987e6 100644
--- a/srcpkgs/MultiMC/template
+++ b/srcpkgs/MultiMC/template
@@ -1,7 +1,7 @@
# Template file for 'MultiMC'
pkgname=MultiMC
version=0.6.12
-revision=2
+revision=3
wrksrc="${pkgname}5-${version}"
_commithashnbt="4b305bbd2ac0e7a26987baf7949a484a87b474d4"
_nbtversion="multimc-0.6.1"
@@ -23,6 +23,10 @@ checksum="c251744b77d93db4ead56940b7b81d30dc5390fb86a1676d3f0364cc4e570185
ffa60368b1c196859691b637c740f4c60597b2ac47217995082ae8b2a3a9ac18"
skip_extraction="${_nbtversion}.tar.gz ${_quazipversion}.tar.gz"
+# Restricted since we don't have permissions to ship builds with the
+# MultiMC name, artwork or the API endpoints.
+restricted=yes
+
case "$XBPS_TARGET_MACHINE" in
armv*) broken="https://github.com/MultiMC/MultiMC5/issues/2895";;
esac
next prev parent reply other threads:[~2021-09-16 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 12:23 [PR PATCH] " Duncaen
2021-09-16 12:56 ` q66
2021-09-16 13:16 ` Duncaen [this message]
2021-09-19 7:30 ` fosslinux
2021-09-23 22:14 ` [PR PATCH] [Merged]: " Duncaen
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=20210916131606.TmCe4nvIeZQI_NpjbIaWrpi98pi2iTDLqVFvdQEsSpM@z \
--to=duncaen@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).