From: "Ludovic Courtès" <ludo@gnu.org>
To: Tomas Volf <~@wolfsden.cz>
Cc: 67044@debbugs.gnu.org
Subject: bug#67044: C.utf8 locale cannot be built
Date: Thu, 07 Dec 2023 11:27:04 +0100 [thread overview]
Message-ID: <87zfyme29z.fsf@gnu.org> (raw)
In-Reply-To: <ZWVA0iZhNXLZpfLV@ws> (Tomas Volf's message of "Tue, 28 Nov 2023 02:22:26 +0100")
Hello!
Tomas Volf <~@wolfsden.cz> skribis:
> On 2023-11-27 23:02:26 +0100, Ludovic Courtès wrote:
[...]
>> Now, it would also be nice if C.utf8 were built-in, shipped with the
>> ‘glibc’ package we have (to me that’s the whole point of C.utf8). We
>> should fix that now in ‘core-updates’. Ideas on how to do that?
>
> After short research, I do have an idea. My knowledge of Guix's internals is
> not good enough (yet? :)) to implement it though. And I am not even sure it
> should be done. Anyway here it goes:
>
> 1. Add a phase after 'install that builds and installs the C.utf8 locale, as
> documented here[0].
> 2. Make glibc package add the directory into GUIX_LOCPATH. Since it accepts :
> separated directories, it should be possible, however I am unsure how.
I decided to give it a go:
https://issues.guix.gnu.org/67686
Please do chime in and let me know what you think!
Ludo’.
next prev parent reply other threads:[~2023-12-07 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 14:42 bug#67044: C.utf8 locale cannot be built Tomas Volf
2023-11-27 22:02 ` Ludovic Courtès
2023-11-28 1:22 ` Tomas Volf
2023-12-07 10:27 ` Ludovic Courtès [this message]
[not found] ` <ZXJCpL0u0UoEb8YA@ws>
2023-12-09 14:46 ` bug#67044: [bug#67686] " Ludovic Courtès
2023-12-10 0:57 ` Tomas Volf
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=87zfyme29z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=67044@debbugs.gnu.org \
--cc=~@wolfsden.cz \
/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).