all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Dmitry Alexandrov <321942@gmail.com>
Cc: 27244@debbugs.gnu.org
Subject: bug#27244: Should not $GUIX_LOCPATH belong to ‘glibc-locales’ rather than ‘glibc’?
Date: Mon, 05 Jun 2017 22:39:23 +0200	[thread overview]
Message-ID: <87inka9nk4.fsf@gnu.org> (raw)
In-Reply-To: <87shjf8abx.fsf@gmail.com> (Dmitry Alexandrov's message of "Mon, 05 Jun 2017 04:58:10 +0300")

Hi Dmitry,

Dmitry Alexandrov <321942@gmail.com> skribis:

> As of now [0] a search path ‘GUIX_LOCPATH’ is exported when ‘glibc’
> package, which does not comprise any locales, is installed.  I guess,
> it should belong to ‘glibc-locales’ and ‘glibc-utf8-locales’ instead.

The idea of search path specifications like ‘GUIX_LOCPATH’ is that the
package that honors them defines them.

For example, Python defines ‘PYTHONPATH’, Guile defines
‘GUILE_LOAD_PATH’, and so on.

In this case, ‘GUIX_LOCPATH’ is honored by glibc, so glibc defines it.

If instead ‘glibc-utf8-locales’ defined it, then you’d immediately get
the recommendation about setting ‘GUIX_LOCPATH’, which I guess is what
you’d like to see.  However, every locale-providing package would need
to define it, which is not great.

On a related note, see this issue about indirect search path
specifications: <https://bugs.gnu.org/22138>.

Does it make sense?

Thanks for your message,
Ludo’.

  reply	other threads:[~2017-06-05 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  1:58 bug#27244: Should not $GUIX_LOCPATH belong to ‘glibc-locales’ rather than ‘glibc’? Dmitry Alexandrov
2017-06-05 20:39 ` Ludovic Courtès [this message]
2017-06-06  1:33   ` Dmitry Alexandrov
2017-06-06 22:57     ` Ludovic Courtès
2017-06-07  7:06       ` Dmitry Alexandrov
2017-06-07  9:40         ` 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=87inka9nk4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27244@debbugs.gnu.org \
    --cc=321942@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 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.