Github messages for voidlinux
 help / color / mirror / Atom feed
From: linkert <linkert@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: font-iosevka: missing Curly & proportional fonts
Date: Tue, 04 Aug 2020 07:33:34 +0200	[thread overview]
Message-ID: <20200804053334.5AxjpaUZwNz6Md-CshgYkRw-lJOCCEyFVDi_0M86BWk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22166@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 808 bytes --]

New comment by linkert on void-packages repository

https://github.com/void-linux/void-packages/issues/22166#issuecomment-668388914

Comment:
> > What's the Void stance on font packages?
> 
> We think they do not [need](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements) to be packaged as pure data.

I would then suggest putting this stance into practice and purging all non-required fonts-, icons- and theme packages (and whatever else might be in the repo that does not fit). That way I won't go all happy when I see a package for Iosevka only to be let down by the fact that it's a dismembered dud of a package.

It's a sound policy and stance which I agree with for the most part - but I could see "popular demand" as an addition - might submit a PR :) 




      parent reply	other threads:[~2020-08-04  5:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 13:12 [ISSUE] " 0n-s
2020-05-22 11:35 ` MatthiasGrandl
2020-05-24  1:32 ` georgianfire
2020-05-24  5:22 ` MatthiasGrandl
2020-08-03 10:17 ` linkert
2020-08-03 10:18 ` linkert
2020-08-03 20:49 ` [ISSUE] [CLOSED] " Chocimier
2020-08-03 20:49 ` Chocimier
2020-08-04  4:47 ` linkert
2020-08-04  5:20 ` Chocimier
2020-08-04  5:33 ` linkert [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=20200804053334.5AxjpaUZwNz6Md-CshgYkRw-lJOCCEyFVDi_0M86BWk@z \
    --to=linkert@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).