unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: 24442@debbugs.gnu.org
Subject: bug#24442: gettext: No PO mode for Emacs (or wrong description)
Date: Sat, 24 Sep 2016 10:55:35 +0900	[thread overview]
Message-ID: <87lgyigiy0.fsf@gnu.org> (raw)
In-Reply-To: <87r38g5krf.fsf@gmail.com> (Alex Kost's message of "Mon, 19 Sep 2016 11:58:12 +0300")

Hi!

Alex Kost <alezost@gmail.com> skribis:

> Ivan Vilata i Balaguer (2016-09-15 09:04 +0200) wrote:
>
>> The description for ``gettext@0.19.8`` (current) includes this sentence:
>>
>>     It provides translators with the means to create message catalogs,
>>     as well as an Emacs mode to work with them, and a runtime library to
>>     load translated messages from the catalogs.
>>
>> However, no output of the package includes the files for Emacs.
>
> Thanks for the report!  This happens because there is no emacs
> dependency (input) in 'gettext' package definition, so Emacs is not
> found during 'configure' phase (as can be seen in the log¹: «checking
> for emacs... no»), so elisp files are not compiled and installed.
>
> I would say this can simply be fixed by adding:
>
>   (native-inputs `(("emacs" ,emacs-minimal)))
>
> to the gettext package definition (also (gnu packages emacs) module
> should be used), and I checked it by making a variant of the gettext
> package with this line; however when I tried it on a real gettext
> package, I saw that a whole world will be rebuilt (apparently it is a
> 'core-updates' thing).  And I realized that emacs (even its minimal
> variant) will probably be a too heavy dependency for such a core thing.
>
> So perhaps it is time to make 'gettext-minimal' and to use it as the
> dependency for other packages and 'gettext' (with Emacs tools) intended
> to be installed by users (as it is done for bash/bash-minimal).  WDYT?
> (this is a question for Guix developers)

I think it’s a good idea; in commencement.scm, we’ll need to inherit
from gettext-minimal to avoid the Emacs dependency.

Most of the packages that currently depend on gettext will have to be
changed to gettext-minimal, as you wrote.

When that it’s done, we can happily add all sorts of dependencies to
gettext, including additional languages for which it provides bindings.

Sounds like a plan no?

Another option would be to hack a phase that copies the .el files to the
output, without compiling them, but I don’t think it’s as nice as the
above plan.

Thanks,
Ludo’.

  reply	other threads:[~2016-09-24  2:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15  7:04 bug#24442: gettext: No PO mode for Emacs (or wrong description) Ivan Vilata i Balaguer
2016-09-19  8:58 ` Alex Kost
2016-09-24  1:55   ` Ludovic Courtès [this message]
2016-09-25  8:09     ` Alex Kost
2016-09-29  8:03 ` Alex Kost
2016-09-29 11:15   ` Ivan Vilata i Balaguer
2016-11-17 14:56     ` Ivan Vilata i Balaguer
2016-11-18  9:36       ` 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=87lgyigiy0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=24442@debbugs.gnu.org \
    --cc=alezost@gmail.com \
    /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).