all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Timo Eisenmann <eisenmann@fn.de>
To: ludo@gnu.org
Cc: 32811@debbugs.gnu.org
Subject: [bug#32811] [PATCH] enlightenment.scm: Fix initial locale and keyboard selection
Date: Tue, 25 Sep 2018 12:51:18 +0200	[thread overview]
Message-ID: <909e244a-1fb7-361b-63b1-9e70bc042e53@fn.de> (raw)
In-Reply-To: <877ejau1z2.fsf@gnu.org>

Hello Ludo,

 >>> Could you explain the effect of adding glibc as an input?  Normally 
this
 >>> is unnecessary because glibc is an implicit input.
 >>
 >> glibc provides locale, which enlightenment uses to list 
languages.Without explicitly installing it, no languages are shown.
 >
 > OK, I see.  However, ‘locale’ is already present in the build
 > environment even without adding glibc explicitly. Thus I wonder what’s
 > happening.

So implicit inputs provide their binaries only during build-time?
Enlightenment actually uses the output of 'locale -a' during runtime.

 > Do you happen to know what part of the Enlightenment code refers to the
 > ‘locale’ command?

Enlightenment uses
   output = popen("locale -a", "r");
in these three files:
   src/bin/e_intl.c (_e_intl_locale_system_locales_get)
   src/modules/conf_intl/e_int_config_intl.c (_fill_data)
   src/modules/wizard/page_010.c (wizard_page_init)

'page_010' is the language selection screen during first time config.

Regards,
Timo Eisenmann

  reply	other threads:[~2018-09-25 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-23 13:22 [bug#32811] [PATCH] enlightenment.scm: Fix initial locale and keyboard selection Timo Eisenmann
2018-09-24 12:28 ` Ludovic Courtès
2018-09-24 15:39 ` eisenmann
2018-09-24 19:31   ` Ludovic Courtès
2018-09-25 10:51     ` Timo Eisenmann [this message]
2018-09-26  7:36       ` Ludovic Courtès
2018-09-26 15:37         ` Timo Eisenmann
2018-09-26 21:41           ` bug#32811: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=909e244a-1fb7-361b-63b1-9e70bc042e53@fn.de \
    --to=eisenmann@fn.de \
    --cc=32811@debbugs.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 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.