All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Hilliard <james.hilliard1@gmail.com>
To: buildroot@buildroot.org
Cc: James Hilliard <james.hilliard1@gmail.com>
Subject: [Buildroot] [PATCH 1/1] system: generate and set C.UTF-8 locale by default
Date: Tue, 17 May 2022 13:24:39 -0600	[thread overview]
Message-ID: <20220517192439.1034654-1-james.hilliard1@gmail.com> (raw)

Now that glibc/localedef supports the C.UTF-8 locale we should default
to it as software like systemd generally expects it to be the locale
used.

This should in general reduce the amount of locale related
compatibility issues and is what many distros have been using for
their default locale for quite a few years so it should be a well
tested configuration.

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
 system/Config.in | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/system/Config.in b/system/Config.in
index 888c24ce81..7cc529d31e 100644
--- a/system/Config.in
+++ b/system/Config.in
@@ -440,7 +440,7 @@ config BR2_ENABLE_LOCALE_PURGE
 
 config BR2_ENABLE_LOCALE_WHITELIST
 	string "Locales to keep"
-	default "C en_US"
+	default "C.UTF-8"
 	depends on BR2_ENABLE_LOCALE_PURGE
 	help
 	  Whitespace seperated list of locales to allow on target.
@@ -455,7 +455,7 @@ config BR2_ENABLE_LOCALE_WHITELIST
 
 config BR2_GENERATE_LOCALE
 	string "Generate locale data"
-	default ""
+	default "C.UTF-8"
 	depends on \
 		(BR2_TOOLCHAIN_BUILDROOT_UCLIBC && BR2_ENABLE_LOCALE) || \
 		BR2_TOOLCHAIN_USES_GLIBC
-- 
2.25.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-05-17 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 19:24 James Hilliard [this message]
2022-05-18 18:27 ` [Buildroot] [PATCH 1/1] system: generate and set C.UTF-8 locale by default Arnout Vandecappelle
2022-05-18 23:15   ` James Hilliard
2022-07-26 21:41 ` Thomas Petazzoni via buildroot

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=20220517192439.1034654-1-james.hilliard1@gmail.com \
    --to=james.hilliard1@gmail.com \
    --cc=buildroot@buildroot.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 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.