public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wiktor Wandachowicz <siryes@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: et_EE locale and language of error messages
Date: Mon, 22 May 2006 16:57:37 +0000 (UTC)	[thread overview]
Message-ID: <loom.20060522T184405-153@post.gmane.org> (raw)
In-Reply-To: 446D9C71.7060703@gentoo.org

Marc Hildebrand <zypher <at> gentoo.org> writes:

> > What do you think? LC_ALL=C in portage or not?
> > 
> > - Stefan
> 
> Well this problem (localized error messages) exists since I know linux 
> and the solution has always been "use per user locale settings and keep 
> LC_ALL=POSIX or =C as a system default".
> Maybe we should just update the docs?

A bug regarding this issue has been filled:
http://bugs.gentoo.org/show_bug.cgi?id=134032

>From the current state of portage code, the patch in question while useful is
not necessary. Portage already defines in /usr/lib/portage/portage_const.py:

USER_CONFIG_PATH        = "/etc/portage"
EBUILD_SH_ENV_FILE      = USER_CONFIG_PATH+"/bashrc"

which is then used in /usr/lib/pym/portage.py:

mysettings["PORTAGE_BASHRC"] = EBUILD_SH_ENV_FILE

and consequently in /usr/lib/bin/ebuild.sh:

if [ -f "${PORTAGE_BASHRC}" ]; then
        source "${PORTAGE_BASHRC}"
fi

So, if the documentation is updated (and possibly advertized in next GWN), no
change (even small) is necessary.

And while I can voice my (user's) opinion, I *really* like the idea of forcing
the sane emerge environment by this one-liner. So in fact I'm torn apart...

Wiktor Wandachowicz
(SirYes)


-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-05-22 17:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  9:38 [gentoo-dev] et_EE locale and language of error messages Stefan Schweizer
2006-05-19 10:22 ` Marc Hildebrand
2006-05-19 13:13   ` [gentoo-dev] " Stefan Schweizer
2006-05-19 13:30     ` Harald van Dijk
2006-05-19 16:01     ` Duncan
2006-05-19 17:14     ` Marius Mauch
2006-05-19 17:27       ` [gentoo-dev] " Stefan Schweizer
2006-05-19 18:10         ` Marius Mauch
2006-05-19 17:45       ` [gentoo-dev] " Zac Medico
2006-05-22 16:57   ` Wiktor Wandachowicz [this message]
2006-05-19 12:49 ` [gentoo-dev] " Harald van Dijk
2006-05-19 13:02   ` Jakub Moc
2006-05-19 13:09   ` Patrick McLean
2006-05-19 13:24     ` Harald van Dijk
2006-05-19 13:55       ` Carsten Lohrke
2006-05-19 13:44   ` Daniel Drake
2006-05-19 13:40     ` Harald van Dijk
2006-05-19 15:44   ` [gentoo-dev] " Stefan Schweizer
2006-05-19 16:05     ` Harald van Dijk
2006-05-24  0:59 ` [gentoo-dev] " Mike Frysinger
2006-05-24 10:36 ` Kevin F. Quinn
2006-05-24 11:17   ` Harald van Dijk
2006-05-24 12:58     ` Kevin F. Quinn
2006-05-24 11:42   ` Jakub Moc
2006-05-24 13:12     ` Kevin F. Quinn
2006-05-25 21:09     ` Mike Frysinger
2006-05-26  7:37     ` Mike Frysinger

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=loom.20060522T184405-153@post.gmane.org \
    --to=siryes@gmail.com \
    --cc=gentoo-dev@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