all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Rohleder <mike@rohleder.de>
To: 45309@debbugs.gnu.org
Subject: [bug#45309] [PATCH] gnu: font-google-roboto: Unzip fonts to a directory.
Date: Fri, 18 Dec 2020 04:34:31 +0100	[thread overview]
Message-ID: <20201218033431.10787-1-mike@rohleder.de> (raw)

* gnu/packages/fonts.scm (font-google-roboto)[arguments]: Add phase to unpack
to a directory and ignore macosx files.
---
After commit e93ee2547ecec152f9a198ccc338c4329cc69a71 this pkg doesn't contain anything.
The difference to the version before is that the upstream zip file doesn't
contain a subfolder anymore, so this patch unpacks to one (and excludes macosx
files while at it).

Maybe the roboto-hinted.zip is better than unhinted? Idk.

 gnu/packages/fonts.scm | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/gnu/packages/fonts.scm b/gnu/packages/fonts.scm
index 717656d682..72e97d99ea 100644
--- a/gnu/packages/fonts.scm
+++ b/gnu/packages/fonts.scm
@@ -801,6 +801,15 @@ display all Unicode symbols.")
        (sha256
         (base32 "0a57f957qy49kildqx2lp2paqk9i8kkayakmrzxh39hhhmqlrxkh"))))
     (build-system font-build-system)
+    (arguments
+     '(#:phases
+       (modify-phases %standard-phases
+         (replace 'unpack
+           (lambda* (#:key inputs #:allow-other-keys)
+             (invoke "unzip" (assoc-ref inputs "source")
+                     "-x" "__MACOSX/*"
+                     "-d" "roboto-unhinted")
+             #t)))))
     (home-page "https://github.com/google/roboto")
     (synopsis "The Roboto family of fonts")
     (description
-- 
2.29.2





             reply	other threads:[~2020-12-18  3:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18  3:34 Michael Rohleder [this message]
2020-12-18  5:27 ` [bug#45309] [PATCH] gnu: font-google-roboto: Unzip fonts to a directory Michael Rohleder
2021-01-12  9:12 ` Nicolas Goaziou
2021-01-12  9:31   ` Michael Rohleder

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=20201218033431.10787-1-mike@rohleder.de \
    --to=mike@rohleder.de \
    --cc=45309@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.