From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: `Package request:` Ventoy - Bootable USB Solution
Date: Sat, 23 Jul 2022 19:03:48 +0200 [thread overview]
Message-ID: <20220723170348.YJqqjfc1GPzlcQbfFryAk2z-QFm9litFYJITgIclU2w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37999@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/37999#issuecomment-1193156308
Comment:
> Why create a package if there are working binary?
1. **compatibility**: void has musl, which almost no upstream creates binaries for, and sometimes upstream-created binaries will link to different versions of libraries than void has (or statically link to them, which is largely a waste of space)
2. **hardening and optimisation**: void enables a set of compiler flags that ensure packages have certain optimisations, hardening measures, and compatibility with all possible targets
3. **ease of use for users**: having a package in the repos means users don't have to manually deal with updates aside from `xbps-install -Su`
4. **trust**: users don't have to decide whether they trust the binaries from some random dev's download page if they choose to trust the maintainers of their distro
next prev parent reply other threads:[~2022-07-23 17:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 12:59 [ISSUE] " pc00per
2022-07-13 10:15 ` wael444
2022-07-13 10:26 ` wael444
2022-07-13 10:34 ` pc00per
2022-07-13 10:34 ` wael444
2022-07-13 11:10 ` wael444
2022-07-13 11:34 ` pc00per
2022-07-14 6:58 ` classabbyamp
2022-07-14 7:20 ` wael444
2022-07-23 15:38 ` Ved-un
2022-07-23 16:52 ` pc00per
2022-07-23 16:53 ` pc00per
2022-07-23 17:03 ` classabbyamp [this message]
2022-07-23 18:21 ` pc00per
2022-07-23 18:23 ` pc00per
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=20220723170348.YJqqjfc1GPzlcQbfFryAk2z-QFm9litFYJITgIclU2w@z \
--to=classabbyamp@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).