all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rovanion Luckey <rovanion.luckey@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Rename glibc-utf8-locales to glibc-limited-utf8-locales
Date: Tue, 8 Feb 2022 10:59:18 +0100	[thread overview]
Message-ID: <CAAaf0CCK-XTzGQ-PHM7RPWPEDtV1K0rg2P6-KHXrsXXHEZhs4g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

Hi,
I have on different occasions had the issue of the package manager Guix
hinting that locales were not installed or that GUIX_LOCPATH was not set,
even though they were. Today I went to the bottom of the issue [0] and have
found what in my opinion is the root cause:

Despite its name, the package glibc-utf8-locales does not contain all
utf8-locales. There is nothing in the name that makes this apparent to the
user, especially given that the package named glibc-locales contains all
locales.

My suggestion then is to change this package name from glibc-utf8-locales
to glibc-limited-utf8-locales to make this distinction apparent to the
user.

The package name was mentioned enough times in the code of guix that I
hesitate to submit a patch with
s/glibc-utf8-locales/glibc-limited-utf8-locales/ run over the codebase. But
perhaps it is that easy.

[0]: https://unix.stackexchange.com/questions/689761

[-- Attachment #2: Type: text/html, Size: 1121 bytes --]

             reply	other threads:[~2022-02-08 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  9:59 Rovanion Luckey [this message]
2022-02-25 18:32 ` Rename glibc-utf8-locales to glibc-limited-utf8-locales Maxim Cournoyer
2022-02-26  7:51   ` Rovanion Luckey
2022-02-26 13:47     ` Maxim Cournoyer
2022-02-26 18:53       ` Rovanion Luckey
2022-02-27  4:16         ` 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=CAAaf0CCK-XTzGQ-PHM7RPWPEDtV1K0rg2P6-KHXrsXXHEZhs4g@mail.gmail.com \
    --to=rovanion.luckey@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.