From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: glibc: clean up install, add C.UTF-8 by default
Date: Wed, 13 Mar 2024 11:46:11 +0100 [thread overview]
Message-ID: <20240313104611.9B2AF269B3@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49146@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
There's a merged pull request on the void-packages repository
glibc: clean up install, add C.UTF-8 by default
https://github.com/void-linux/void-packages/pull/49146
Description:
We should really provide the `C.UTF-8` locale by default. I believe that the best way to do so is by removing it entirely from `/etc/default/libc-locales` processing and install it, as part of the main `glibc` package, in `/usr/lib/locales` like Arch does.
This currently trips the package linter, so either
- We can make an exception for glibc in the linter, or
- Rather than include the locale files in the package, we can add an `INSTALL` script to the base package to write the `C.utf-8` locale outside of an archive, where it will always be reachable.
I favor the first because it is less wasteful; why should everybody have to generate a locale that we expect everybody to have available by default?
A third option is to modify the `glibc-locales` `INSTALL` script to either add a separate, non-archived `C.utf-8` locale directory, or just ensure that `C.UTF-8` is always included in the locale processing. Both seem even more kludgey than doing the right thing by default.
Thoughts? @void-linux/pkg-committers
While I was at it, I cleaned up the install function a bit.
prev parent reply other threads:[~2024-03-13 10:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 13:55 [PR PATCH] " ahesford
2024-03-06 15:44 ` [PR PATCH] [Updated] " ahesford
2024-03-06 15:45 ` ahesford
2024-03-06 16:04 ` [PR PATCH] [Updated] " ahesford
2024-03-06 20:10 ` oreo639
2024-03-06 20:10 ` oreo639
2024-03-06 20:11 ` oreo639
2024-03-06 20:20 ` oreo639
2024-03-06 20:45 ` oreo639
2024-03-06 20:46 ` oreo639
2024-03-06 20:46 ` oreo639
2024-03-06 23:24 ` oreo639
2024-03-06 23:27 ` [PR REVIEW] " oreo639
2024-03-06 23:37 ` oreo639
2024-03-06 23:37 ` oreo639
2024-03-06 23:37 ` oreo639
2024-03-06 23:37 ` oreo639
2024-03-06 23:38 ` oreo639
2024-03-07 0:49 ` [PR PATCH] [Updated] " ahesford
2024-03-07 0:50 ` ahesford
2024-03-07 21:56 ` oreo639
2024-03-07 21:57 ` oreo639
2024-03-07 21:58 ` oreo639
2024-03-07 21:59 ` ahesford
2024-03-07 21:59 ` oreo639
2024-03-13 10:46 ` ahesford [this message]
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=20240313104611.9B2AF269B3@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).