unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Frequent locales problems for new users
Date: Wed, 18 Mar 2020 16:07:22 +0100	[thread overview]
Message-ID: <87eetp8zx1.fsf@gnu.org> (raw)
In-Reply-To: <20200317202843.GA18844@jasmine.lan> (Leo Famulari's message of "Tue, 17 Mar 2020 16:28:43 -0400")

Hello!

Leo Famulari <leo@famulari.name> skribis:

> Warning! Locales! New users seem to have trouble with Guix locales every
> day.
>
> I think we can improve the situation.
>
> First, we can deprecate the glibc-utf8-locales package and not mention
> it in the manual section Application Setup. I've seen users think they
> had to install it in order to get UTF-8 support. Everyone should be
> using glibc-locales. Eventually we can rename it to
> 'glibc-locales-for-tests', and hide the package too.

Well, we still need to be able to install locales somehow, right?  :-)

> Second, we need to make sure that guix-install.sh is setting up
> GUIX_LOCPATH correctly. I see that the binary tarball's store includes
> glibc-utf8-locales, so it should be possible for things to "just work",
> ignoring that it's the wrong locales package. Does anyone know any
> particular issues with the installer that would cause trouble?

‘guix-command’ in (guix self) creates a ‘guix’ binary where GUIX_LOCPATH
points to ‘glibc-utf8-locales’, always.  That means that ‘guix pull’
returns a ‘guix’ program that works fine, provided you use one of the
locales in ‘glibc-utf8-locales’ *or* you have installed ‘glibc-locales’
and set ‘GUIX_LOCPATH’.

The ‘guix’ binary of the ‘guix’ package does something similar.

These two should already eliminate most problems.  Now, we should
investigate actual problems to see why they show up precisely (for that
we need to see the output of commands, the contents of the .service
file, and so on).  That will allow us to determine the best course of
action.

As for ‘glibc-utf8-locales’ vs. ‘glibc-locales’: the reason for choosing
the former by default over the latter is size (14 MiB vs. 917 MiB).
Perhaps an improvement would be for ‘glibc-utf8-locales’ to be more true
to its name: to include all the UTF-8 locales glibc supports rather than
an arbitrary sample thereof.

Thoughts?

Ludo’.

  parent reply	other threads:[~2020-03-18 15:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 20:28 Frequent locales problems for new users Leo Famulari
2020-03-18  7:47 ` Efraim Flashner
2020-03-18  8:12 ` Thorsten Wilms
2020-03-18 16:22   ` Tobias Geerinckx-Rice
2020-03-18 15:07 ` Ludovic Courtès [this message]
2020-03-18 18:36   ` Leo Famulari
2020-03-21 15:37     ` Ludovic Courtès
2020-03-21 18:02       ` Gábor Boskovits
2020-03-21 19:43       ` Leo Famulari
2020-03-21 20:14         ` Leo Famulari
2020-03-26 12:06         ` Ludovic Courtès
2020-07-01 18:02 ` Vagrant Cascadian

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=87eetp8zx1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).