unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: gettext: Enable "xgettext --language=glade"
Date: Mon, 18 Nov 2013 09:17:03 +0100	[thread overview]
Message-ID: <20131118081703.GA28696@debian> (raw)
In-Reply-To: <877gc639c3.fsf@gnu.org>

On Mon, Nov 18, 2013 at 12:19:24AM +0100, Ludovic Courtès wrote:
> Actually, it seems to be solvable without adding the dependency:
> 
> --8<---------------cut here---------------start------------->8---
> $ xgettext -L glade /dev/null 
> xgettext: Language "glade" is not supported. xgettext relies on expat.
>           This version was built without expat.
> 
> $ LD_LIBRARY_PATH=$(guix build expat)/lib xgettext -L glade /dev/null 
> xgettext: /dev/null:1:1: no element found
> --8<---------------cut here---------------end--------------->8---

I know, that was one of the things we tested early on; but...

> Would it work for you to just use that LD_LIBRARY_PATH trick where it’s
> needed?
> That way we avoid making gettext “fatter”.  I suppose we’ll seldom need
> to do that trick anyway.

... might there not be users who want a fully functional xgettext? Now that
we found a simple solution, I am rather in favour of implementing it.
Not to mention that this solves the issue once and for all, and we do not
need to remember the LD_LIBRARY_PATH trick later on...

Andreas

  reply	other threads:[~2013-11-18  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17 12:25 [PATCH] gnu: gettext: Enable "xgettext --language=glade" Andreas Enge
2013-11-17 21:00 ` Ludovic Courtès
2013-11-17 23:19 ` Ludovic Courtès
2013-11-18  8:17   ` Andreas Enge [this message]
2013-11-18  9:17     ` Ludovic Courtès
2013-11-18  9:58       ` Andreas Enge
2013-11-18 10:05         ` Andreas Enge
2013-11-18 12:58         ` 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=20131118081703.GA28696@debian \
    --to=andreas@enge.fr \
    --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).