unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: iyzsong@member.fsf.org (宋文武)
To: "alírio eyng" <alirioeyng@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build from source.
Date: Mon, 28 Mar 2016 21:40:47 +0800	[thread overview]
Message-ID: <87k2kmn2jk.fsf@member.fsf.org> (raw)
In-Reply-To: <CALkz57HFovcgWx4PdyW_LZck4f24rS+Q=7gwiivu5V3gCX0tEQ@mail.gmail.com> ("alírio eyng"'s message of "Sat, 26 Mar 2016 14:47:09 +0000")

alírio eyng <alirioeyng@gmail.com> writes:

> From dac1dfe1d9b6716d1aefa339e5145c26dd798565 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?al=C3=ADrio=20eyng?= <alirioeyng@gmail.com>
> Date: Sat, 26 Mar 2016 14:39:27 +0000
> Subject: [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build from
>  source.
Cool!
>
> * gnu/packages/fonts.scm (font-gnu-freefont-ttf): Update to 20120503.
> [arguments]: Build from source.
> * guix/gnu-maintenance.scm (%tarball-rx): Remove comment.
Not clear, how about “Remove comment about freefont-ttf.”?
> […]
> +    (native-inputs `(("fontforge" ,(package (inherit fontforge)
> +                                     (inputs `(("python-2" ,python-2)
> +                                     ,@(package-inputs fontforge)))))))
Why not add ‘python-2’ to the fontforge package directly?


Thanks!

  reply	other threads:[~2016-03-28 13:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-26 14:47 [PATCH] gnu: font-gnu-freefont-ttf: Update to 20120503 and build from source alírio eyng
2016-03-28 13:40 ` 宋文武 [this message]
2016-03-29  3:38   ` alírio eyng
2016-03-31  7:48     ` Ludovic Courtès
2016-03-31 13:18       ` alírio eyng
2016-03-31 21:45         ` Ludovic Courtès
2016-04-02  8:39         ` Eric Bavier
2016-04-02 10:38           ` alírio eyng
2016-04-03 21:47             ` Ludovic Courtès
2016-04-04 14:19               ` alírio eyng

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=87k2kmn2jk.fsf@member.fsf.org \
    --to=iyzsong@member.fsf.org \
    --cc=alirioeyng@gmail.com \
    --cc=guix-devel@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).