From: Ada Stevenson <adanskana@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: Is installing `glibc-locales` necessary on GuixSD?
Date: Mon, 2 Sep 2024 05:38:24 +0000 [thread overview]
Message-ID: <01aaa7f1-3f26-4ed8-b63e-b912f20e2bca@gmail.com> (raw)
In-Reply-To: <e49756e9-4b8a-4edc-a50c-d891728761da@gmail.com>
Hi Guix...
This is embarrassing. I sent this email before I actually reconfigured
my system, and it seems like the message has gone away and the locales
are working....... oops!
Please disregard this message!
On 01/09/2024 6:57 am, Ada Stevenson wrote:
> Hi Guix!
>
> Congratulations to everyone who worked on the core-updates merge!
>
> A lot of things have changed though, and I was curious about this new
> message I've been getting whenever I invoke `guix`.
>
>> hint: Consider installing the `glibc-locales' package and defining
>> `GUIX_LOCPATH', along these lines:
>>
>> guix install glibc-locales
>> export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
>>
>> See the "Application Setup" section in the manual, for more info.
>
> I've looked at the section in the manual, and it essentially reiterates
> the message here. For me, this is strange. The benefit of using GuixSD
> is that stuff like this is handled for me - things like search paths and
> the like that need to be taken care of separately on a foreign
> distribution are pre-configured here.
>
> I feel like this new locale change should be one of these things that is
> handled by GuixSD, somehow incorporated into `%base-packages` and the
> environment variables set in the default `.profile` script like the
> other Guix specific env-vars.
>
> What do you all think?
>
> Warmly,
> Ada
Warmly,
Ada
next prev parent reply other threads:[~2024-09-02 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 6:57 Is installing `glibc-locales` necessary on GuixSD? Ada Stevenson
2024-09-02 5:38 ` Ada Stevenson [this message]
2024-09-06 8:49 ` Ludovic Courtès
2024-12-15 3:10 ` Maxim Cournoyer
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=01aaa7f1-3f26-4ed8-b63e-b912f20e2bca@gmail.com \
--to=adanskana@gmail.com \
--cc=guix-devel@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.