From: "Antonin Godard" <antonin.godard@bootlin.com>
To: quentin.schulz@cherry.de,
"Guénaël Muller" <guenael.muller@smile.fr>,
docs@lists.yoctoproject.org
Cc: "Yoann Congal" <yoann.congal@smile.fr>
Subject: Re: [docs] [PATCH v2] ref-manual: use standardized method accross both ubuntu and debian for locale install
Date: Wed, 20 Nov 2024 17:43:03 +0100 [thread overview]
Message-ID: <D5R5N6X7BUEX.2BBRC9BZR37GE@bootlin.com> (raw)
In-Reply-To: <299a188d-c7a9-4604-a491-9efb3888e7ba@cherry.de>
Hi Guénaël, Quentin,
On Tue Nov 19, 2024 at 10:28 AM CET, Quentin Schulz via lists.yoctoproject.org wrote:
[...]
>>> +You also need to ensure you have the locale ``en_US.UTF-8`` enabled::
>>> +
>
> I believe "the ``en_US.UTF-8`` locale" is more proper here.
>
> On a side note, what's the actual cost of reconfiguring the locales
> regardless of the presence of en_US.UTF-8?
>
> My point being we could probably have this command in poky.yaml.in like
> it used to be?
>
>>> + $ locale --all-locales | grep en_US.utf8
>>> +
>>> +If this is not the case, you can reconfigure the ``locales`` package to add it::
>>> +
>>> + $ sudo dpkg-reconfigure locales
>>> +
>
> How does this actually generate en_US.utf8 locale if we don't explicitly
> add it somewhere? Are you sure it's not because your system has LANG or
> LC_ALL set to that locale and then calling reconfigure it regenerate it?
>
> Also on a side note we tell people to check if "en_US.UTF-8" locale is
> enabled by grepping for "en_US.utf8", is that expected? Why aren't they
> the same?
Yes, "locale --all-locales" does return "en_US.utf8" while we install the
"en_US.UTF-8" locale (different string, not sure why).
I seem to be able to build with both Debian/Ubuntu with this command:
LANG="en_US.UTF-8" locale-gen
Maybe this is a more straightforward approach, closer to what we had before.
What do you think? Guénaël would you be able to update your patch with this
command if this works for you too?
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-11-20 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 10:45 [PATCH v2] ref-manual: use standardized method accross both ubuntu and debian for locale install Guénaël Muller
2024-11-18 11:00 ` Antonin Godard
2024-11-19 9:28 ` [docs] " Quentin Schulz
2024-11-20 16:43 ` Antonin Godard [this message]
2024-11-22 9:25 ` Guénaël MULLER
2024-11-25 8:07 ` Antonin Godard
2024-11-25 10:19 ` Quentin Schulz
2024-11-25 14:39 ` Guénaël MULLER
2024-11-27 8:34 ` Antonin Godard
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=D5R5N6X7BUEX.2BBRC9BZR37GE@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=guenael.muller@smile.fr \
--cc=quentin.schulz@cherry.de \
--cc=yoann.congal@smile.fr \
/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