From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: macchina-0.9.2
Date: Thu, 17 Jun 2021 17:49:35 +0200 [thread overview]
Message-ID: <20210617154935.vGJCvcXEQkjNCAiMK0MWxenJpmlSFA3_zKCnqtvXHV4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31361@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/31361#issuecomment-863355995
Comment:
FWIW, considering rust's overall hostility against distribution packaging (no way to manage dependencies outside of cargo, no dynamic linking of rust libraries, no reasonable way to control fetching of distfiles and so on) i believe the majority of these other rust programs in the repository shouldn't have been packaged either (other distributions in general do not package them)
if there's something we definitely do not need, it's a multitude of *fetch programs that all serve the purpose of making fancy screenshots for /r/unixporn
also fwiw, a program with 158 dependencies and 7.5MB binary size can hardly be considered minimalistic (and regardless of the functionality it implements, it's ridiculous for a *fetch program) and literally noone cares about whether a fetch takes 10ms or 150ms (not to mention that benchmarking against what is literally a shell script - neofetch - is pretty amusing)
so yeah, i still don't see a reason to package every single rust program under the sun especially considering the rust project seemingly does not care for providing reasonable means of packaging them
next prev parent reply other threads:[~2021-06-17 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 12:24 [PR PATCH] " machadofguilherme
2021-06-08 18:08 ` Chocimier
2021-06-08 18:08 ` [PR PATCH] [Closed]: " Chocimier
2021-06-08 20:36 ` machadofguilherme
2021-06-08 21:23 ` q66
2021-06-08 21:24 ` q66
2021-06-17 14:22 ` eoli3n
2021-06-17 14:41 ` q66
2021-06-17 14:56 ` eoli3n
2021-06-17 15:11 ` grtcdr
2021-06-17 15:49 ` q66 [this message]
2021-06-17 16:15 ` grtcdr
2021-06-17 16:20 ` grtcdr
2021-06-17 16:23 ` ahesford
2021-06-17 16:24 ` Chocimier
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=20210617154935.vGJCvcXEQkjNCAiMK0MWxenJpmlSFA3_zKCnqtvXHV4@z \
--to=q66@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).