From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add xfd.
Date: Sat, 02 Jul 2016 20:50:50 +0300 [thread overview]
Message-ID: <87mvm09bet.fsf@gmail.com> (raw)
In-Reply-To: <87vb0ogo9w.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 02 Jul 2016 15:31:07 +0200")
Ludovic Courtès (2016-07-02 16:31 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> * gnu/packages/xorg.scm (xfd): New variable.
>
> [...]
>
>> + (native-inputs
>> + `(("gettext" ,gnu-gettext)
>
> Is Gettext really needed?
I think so, without gettext the build fails.
--
Alex
next prev parent reply other threads:[~2016-07-02 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 18:18 [PATCH 1/2] gnu: Add xfontsel Alex Kost
2016-06-30 18:18 ` [PATCH 2/2] gnu: Add xfd Alex Kost
2016-07-02 13:31 ` Ludovic Courtès
2016-07-02 17:50 ` Alex Kost [this message]
2016-07-02 13:30 ` [PATCH 1/2] gnu: Add xfontsel Ludovic Courtès
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=87mvm09bet.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).