GNU bug report logs - #27244
Should not $GUIX_LOCPATH belong to ‘glibc-locales’ rather than ‘glibc’?

Previous Next

Package: guix;

Reported by: Dmitry Alexandrov <321942 <at> gmail.com>

Date: Mon, 5 Jun 2017 01:59:02 UTC

Severity: normal

Tags: notabug

Done: ludo <at> gnu.org (Ludovic Courtès)

Bug is archived. No further changes may be made.

Full log


Message #8 received at 27244 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Dmitry Alexandrov <321942 <at> gmail.com>
Cc: 27244 <at> debbugs.gnu.org
Subject: Re: bug#27244: Should not $GUIX_LOCPATH belong to
 ‘glibc-locales’ rather than ‘glibc’?
Date: Mon, 05 Jun 2017 22:39:23 +0200
Hi Dmitry,

Dmitry Alexandrov <321942 <at> 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’.




This bug report was last modified 7 years and 302 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.