all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Danckaert <thomas.danckaert@gmail.com>
To: ludo@gnu.org
Cc: guix-devel@gnu.org, sbaugh@catern.com
Subject: Re: Foreign distro GUIX_LOCPATH errors when installing from manual
Date: Mon, 11 Jul 2016 12:48:34 +0200 (CEST)	[thread overview]
Message-ID: <20160711.124834.855674177386961799.thomas.danckaert@gmail.com> (raw)
In-Reply-To: <87mvlomqrn.fsf@gnu.org>

From: ludo@gnu.org (Ludovic Courtès)
Subject: Re: Foreign distro GUIX_LOCPATH errors when installing from 
manual
Date: Mon, 11 Jul 2016 12:07:56 +0200

>> and that the installation instructions say to install glibc-locale 
>> (or
>> some other locale package) in root's profile.
>
> They already say so under “Application Setup”, but maybe that 
> should be
> made more prominent?

The section does not explicitly tell to install these locales also 
for root.

Perhaps the daemon systemd configuration could be expanded to set a 
specific locale for the Guix build-daemon (currently it uses the host 
systems default locale settings), and a package for only that 
specific locale could be included in the binary tarball, installed in 
root's profile?  I'm not really familiar with the build daemon or 
locales, but I think that it doesn't matter so much which locale is 
set for the build daemon, as long as it is properly configured? (This 
is also related to your question about including glibc-utf8-locales 
in the binary tarball in the parallel thread)

Thomas

  reply	other threads:[~2016-07-11 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 17:07 Foreign distro GUIX_LOCPATH errors when installing from manual sbaugh
2016-07-11 10:07 ` Ludovic Courtès
2016-07-11 10:48   ` Thomas Danckaert [this message]
2016-07-11 18:26   ` Spencer Baugh

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=20160711.124834.855674177386961799.thomas.danckaert@gmail.com \
    --to=thomas.danckaert@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=sbaugh@catern.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.