From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Issue: multiMC
Date: Thu, 16 Sep 2021 14:11:25 +0200 [thread overview]
Message-ID: <20210916121125.evOK9A4IreIsF0836QloZ6FpMQYoYfOu6z7SQBCXIDY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32950@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/32950#issuecomment-920846334
Comment:
I think the best solution here is to make the package restricted, we won't build or ship it and users are free to either download the binaries themselves or use the repository to build the package from source themselves for personal use.
There are a few problems I see with shipping binaries:
* They only support two of the architectures we ship packages for.
* We can't rebuild it if any of the linked shared libraries require a rebuild (not sure how the chances are for that to happen, since its just qt5 and zlib).
* Downloading binaries at install time just results in a bad user experience, completely negating all benefits of using a package manager.
next prev parent reply other threads:[~2021-09-16 12:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 15:05 [ISSUE] " apirusKde
2021-09-13 15:32 ` apirusKde
2021-09-13 15:32 ` apirusKde
2021-09-13 18:11 ` Hnaguski
2021-09-13 18:44 ` Hnaguski
2021-09-14 12:25 ` apirusKde
2021-09-15 0:07 ` apirusKde
2021-09-15 3:37 ` Hnaguski
2021-09-15 7:34 ` kotajacob
2021-09-15 23:42 ` ImperatorStorm
2021-09-15 23:42 ` ImperatorStorm
2021-09-16 12:10 ` Duncaen
2021-09-16 12:11 ` Duncaen [this message]
2021-09-16 20:24 ` Hnaguski
2021-09-19 7:26 ` fosslinux
2021-09-19 7:31 ` fosslinux
2021-09-23 22:04 ` apirusKde
2021-10-11 12:41 ` [ISSUE] [CLOSED] " apirusKde
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=20210916121125.evOK9A4IreIsF0836QloZ6FpMQYoYfOu6z7SQBCXIDY@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).