From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New-package: ttf-nerd-fonts-symbols-3.0.2
Date: Tue, 19 Sep 2023 04:40:59 +0200 [thread overview]
Message-ID: <20230919024059.IcptRDTLA2fSR_CKd-GC21Cr0SpUN_-cRUPNsyU5xSM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46118@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
There's a closed pull request on the void-packages repository
New-package: ttf-nerd-fonts-symbols-3.0.2
https://github.com/void-linux/void-packages/pull/46118
Description:
@cinerea0
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64
WHY?
`nerd-fonts` is a bloated package (2GB, REALLY?) which includes a ton of fonts, and scripts which can't be even executed by a non-root user due to permissions. BTW, these scripts have nothing to do with patching fonts, but with cheat sheet functionality. I don't even understand how it it was allowed into the repository in the first place!
`ttf-nerd-fonts-symbols` is the only part that's truly necessary. It provides unique glyphs. My template includes also `fontconfig` preset.
prev parent reply other threads:[~2023-09-19 2:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 20:42 [PR PATCH] New-package: ttf-nerd-fonts-symbols-3.0.2, removed-packages: revbump due to nerd-fonts{,-ttf,-otf} removal chrysos349
2023-09-18 20:46 ` classabbyamp
2023-09-18 20:48 ` chrysos349
2023-09-18 20:49 ` classabbyamp
2023-09-18 21:03 ` [PR PATCH] [Updated] " chrysos349
2023-09-18 21:06 ` New-package: ttf-nerd-fonts-symbols-3.0.2 chrysos349
2023-09-18 22:52 ` cinerea0
2023-09-18 23:45 ` [PR PATCH] [Updated] " chrysos349
2023-09-18 23:47 ` chrysos349
2023-09-18 23:47 ` chrysos349
2023-09-19 1:48 ` ahesford
2023-09-19 2:40 ` chrysos349 [this message]
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=20230919024059.IcptRDTLA2fSR_CKd-GC21Cr0SpUN_-cRUPNsyU5xSM@z \
--to=chrysos349@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).