unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@infotropique.org>
To: 27958@debbugs.gnu.org
Subject: [bug#27958] [fonts] Add font-fira-sans
Date: Fri, 4 Aug 2017 19:24:28 +0000	[thread overview]
Message-ID: <20170804192428.x55d262ldqjdvxh7@abyayala> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]

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.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

[-- Attachment #1.2: 0001-gnu-add-font-fira-sans.patch --]
[-- Type: text/plain, Size: 1506 bytes --]

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.
---
 gnu/packages/fonts.scm | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/gnu/packages/fonts.scm b/gnu/packages/fonts.scm
index 51073eff9..e009c6a67 100644
--- a/gnu/packages/fonts.scm
+++ b/gnu/packages/fonts.scm
@@ -825,6 +825,24 @@ designed to work well in user interface environments.")
     (description "This is the typeface used by Mozilla in Firefox OS.")
     (license license:silofl1.1)))
 
+(define-public font-fira-sans
+  (package
+    (name "font-fira-sans")
+    (version "4.202")
+    (source (origin
+              (method url-fetch)
+              (uri (string-append "https://github.com/mozilla/Fira/archive/"
+                                  version ".tar.gz"))
+              (file-name (string-append name "-" version ".tar.gz"))
+              (sha256
+               (base32
+                "1r6zdnqqp4bgq5nmgqbj0vvj7x1h9w912851ggbl9wc7fdjnjqnq"))))
+    (build-system font-build-system)
+    (home-page "http://mozilla.github.io/Fira/")
+    (synopsis "Mozilla's Fira Sans Font")
+    (description "This is the typeface used by Mozilla in Firefox OS.")
+    (license license:silofl1.1)))
+
 (define-public font-awesome
   (package
    (name "font-awesome")
-- 
2.13.4


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

             reply	other threads:[~2017-08-04 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 19:24 ng0 [this message]
2017-11-28 18:59 ` [bug#27958] [fonts] Add font-fira-sans ng0
2017-11-28 19:26 ` bug#27958: " Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170804192428.x55d262ldqjdvxh7@abyayala \
    --to=ng0@infotropique.org \
    --cc=27958@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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).