all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 27958-done@debbugs.gnu.org
Subject: bug#27958: [fonts] Add font-fira-sans
Date: Tue, 28 Nov 2017 14:26:59 -0500	[thread overview]
Message-ID: <20171128192659.GC27388@jasmine.lan> (raw)
In-Reply-To: <20170804192428.x55d262ldqjdvxh7@abyayala>

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

On Fri, Aug 04, 2017 at 07:24:28PM +0000, ng0 wrote:
> This is not the canonical upstream source. But the upstream
> source bundles many pdf files (one for each variant I assume) and
> has a layout which makes it impossible to use our font-build-system.
> 
> Mozilla (where the upstream team works with), size: 90.2MiB
> Upstream: 96.6MiB
> 
> Is it still acceptable for us to use github in this case?
> 
> Upstream source is https://carrois.com/typefaces/FiraSans/#!layout=editor
> in case anyone wants to take a look.
> 
> The appended patch uses the github of mozilla as source.

We already fetch Fira Mono from Mozilla, so I'd say this is fine for
now. We can always change it later.

> -- 
> ng0
> GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
> GnuPG: https://n0is.noblogs.org/my-keys
> https://www.infotropique.org https://krosos.org

> From e4c81044bf483891c57a3e7b162baee58f08e526 Mon Sep 17 00:00:00 2001
> From: ng0 <ng0@infotropique.org>
> Date: Fri, 4 Aug 2017 19:13:51 +0000
> Subject: [PATCH] gnu: add font-fira-sans.
> 
> * gnu/packages/fonts.scm (font-fira-sans): New variable.

Pushed as 0ee27df06be40ec63e393f1120ecb87dc825df17

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2017-11-28 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 19:24 [bug#27958] [fonts] Add font-fira-sans ng0
2017-11-28 18:59 ` ng0
2017-11-28 19:26 ` Leo Famulari [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=20171128192659.GC27388@jasmine.lan \
    --to=leo@famulari.name \
    --cc=27958-done@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.