public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  SNIP warning: setlocale: LC_ALL error
Date: Thu, 17 Jul 2014 23:48:51 +0100	[thread overview]
Message-ID: <3256658.0gL6GGCI37@wstn> (raw)
In-Reply-To: <53C84319.5010606@gmail.com>

On Thursday 17 July 2014 16:41:45 Dale wrote:

> This is my locale.gen file:
> 
> LANG="en_US.UTF8"
> LC_CTYPE="en_US.UTF8"
> LC_NUMERIC="en_US.UTF8"
> LC_TIME="en_US.UTF8"
> LC_COLLATE="en_US.UTF8"
> LC_MONETARY="en_US.UTF8"
> LC_MESSAGES="en_US.UTF8"
> LC_PAPER="en_US.UTF8"
> LC_NAME="en_US.UTF8"
> LC_ADDRESS="en_US.UTF8"
> LC_TELEPHONE="en_US.UTF8"
> LC_MEASUREMENT="en_US.UTF8"

Dale, why are you setting all those values yourself? As far as I know, the 
only one you need to set is the first one: LANG. The rest of them should all 
be taken care of by portage - unless you have very particular (i.e. special) 
requirements. I don't have any of those values set anywhere; look:

$ grep -r LC_ /etc
/etc/init.d/hwclock:            if LC_ALL=C hwclock --help 2>&1 | grep -q 
"\-\-noadjfile"; then
/etc/portage/savedconfig/sys-apps/busybox-1.21.0:# CONFIG_FEATURE_IPCALC_FANCY 
is not set
/etc/portage/savedconfig/sys-apps/busybox-1.21.0:# 
CONFIG_FEATURE_IPCALC_LONG_OPTIONS is not set
/etc/ssh/ssh_config:SendEnv LANG LC_*

This is my /etc/locale.gen:

en_GB.UTF-8 UTF-8
en_GB ISO-8859-1
en_GB.ISO-8859-15 ISO-8859-15

I don't remember why I still have those last two entries; I expect they date 
from before Gentoo adopted UTF-8. Maybe I'll remove them and see what happens.

It's an easy trap to fall into: over-specifying details just because Gentoo 
lets you do so, in contrast to other distros.

KISS  :)

-- 
Regards
Peter



  parent reply	other threads:[~2014-07-17 22:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  1:50 [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error Dale
2014-07-15  2:02 ` Hinnerk van Bruinehsen
2014-07-15  2:19   ` Dale
2014-07-15  2:35     ` Hinnerk van Bruinehsen
2014-07-15  3:44       ` Dale
2014-07-15  5:33 ` Dale
2014-07-15  7:04   ` Hinnerk van Bruinehsen
2014-07-15  7:40     ` Dale
2014-07-15  8:15       ` Hinnerk van Bruinehsen
2014-07-15  8:40         ` Hinnerk van Bruinehsen
2014-07-15  9:25           ` Dale
2014-07-15 18:52             ` Douglas J Hunley
2014-07-15 19:18               ` Dale
2014-07-16  7:32             ` Dale
2014-07-16  7:46               ` Helmut Jarausch
2014-07-16  8:43                 ` Dale
2014-07-16  9:19                   ` Dale
2014-07-16 10:33                     ` J. Roeleveld
2014-07-16 15:44                       ` Dark Templar
2014-07-16 17:26                         ` Dale
2014-07-16 21:09                           ` Mick
2014-07-16 21:34                             ` Dale
2014-07-17  4:52                           ` J. Roeleveld
2014-07-17  7:19                             ` J. Roeleveld
2014-07-17  9:03                               ` Dale
2014-07-17  9:19                                 ` J. Roeleveld
2014-07-17 10:45                                   ` J. Roeleveld
2014-07-18  9:18                                     ` Dale
2014-07-18  9:38                                       ` J. Roeleveld
2014-07-18 12:44                                       ` Jc García
2014-07-17  9:20                                 ` Peter Humphrey
2014-07-17 13:24                                   ` Peter Humphrey
2014-07-16 17:21                       ` Dale
2014-07-17  0:39                         ` [gentoo-user] " walt
2014-07-17  1:01                           ` Dale
2014-07-17 21:41 ` [gentoo-user] SNIP " Dale
2014-07-17 22:08   ` Mick
2014-07-18  3:55     ` Dale
2014-07-18  4:32       ` Jc García
2014-07-17 22:48   ` Peter Humphrey [this message]
2014-07-18  5:54     ` Mick
2014-07-18  8:12       ` 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=3256658.0gL6GGCI37@wstn \
    --to=peter@prh.myzen.co.uk \
    --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