public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] /etc/locale vs /etc/env.d/02locale?
Date: Thu, 16 Jun 2011 09:23:16 -0700	[thread overview]
Message-ID: <BANLkTinPXJUwj_94fecSWO6A+nJOJX0JvQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikP=J_NeFs-LhYb3RPANhDr74+icg@mail.gmail.com>

On Thu, Jun 16, 2011 at 9:00 AM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Thu, Jun 16, 2011 at 10:45 AM, Mark Knecht <markknecht@gmail.com> wrote:
>> Is there a simple explanation concerning the difference between the
>> two locales I have seen on Gentoo machines?
>>
>> 1) /etc/locale, as specified in the installation documents
>>
>> 2) /etc/env.d/02locale as has been discussed on the list recently
>
> I'm not near a Gentoo machine right now, but off the top of my head IIRC:
>
> /etc/locale.gen contains a list of locales to be compiled when glibc
> is emerged. These will be available to be used.
>
> /etc/env.d/02locale specifies which of those locales you actually want
> to use for the system-wide default (the LC variables)

Thanks for the response Paul.

Does that mean that the /etc/locale.gen is used only by glibc and not
really by the system? If so, what is glibc doing with these beyond
letting me system run programs?

If 02locale specifies what the system is using, then should it be
02locale that's in the install documents vs off in an optional Gentoo
Localization guide?

Note that the /etc/locale.gen stuff is marked optional in the guide so
presumably it isn't actually needed. All I've determined about it is
that it reduces the amount of time emerge spends buildingglibc/gcc.

Thanks,
Mark



  parent reply	other threads:[~2011-06-16 17:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 15:45 [gentoo-user] /etc/locale vs /etc/env.d/02locale? Mark Knecht
2011-06-16 16:22 ` [gentoo-user] " Nikos Chantziaras
2011-06-16 16:45   ` Mark Knecht
2011-06-16 16:54     ` Nikos Chantziaras
     [not found] ` <BANLkTikP=J_NeFs-LhYb3RPANhDr74+icg@mail.gmail.com>
2011-06-16 16:23   ` Mark Knecht [this message]
2011-06-16 16:47     ` Nikos Chantziaras
2011-06-16 16:56     ` [gentoo-user] " YoYo Siska
     [not found]     ` <BANLkTimqq_f+69OMmDeZGwvBvX349xUCtg@mail.gmail.com>
2011-06-18  0:50       ` [gentoo-user] " walt
2011-06-18  1:35         ` Nikos Chantziaras
2011-06-18  1:46         ` Peter Humphrey
2011-06-18 21:03           ` walt
2011-06-19 20:46           ` Walter Dnes
2011-06-19 21:47             ` Peter Humphrey

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=BANLkTinPXJUwj_94fecSWO6A+nJOJX0JvQ@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.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