From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Disabling locale at emerge output
Date: Fri, 22 Apr 2011 19:53:36 +0200 [thread overview]
Message-ID: <201104221953.36951.dilfridge@gentoo.org> (raw)
In-Reply-To: <BANLkTikc+7JQcdd21dLuv7WEYgii9tYFfA@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1785 bytes --]
How about a portage "feature" that is off by default? Like, "locale" meaning
"build with locale"?
If it is on, and a build fails, the default error message could be extended
with something like
"Note that this build was using your system locale, i.e. the error messages
are in your language and may not be understood by the developers or
maintainers. If you want to file a bug, please re-emerge with FEATURE=-locale"
Am Freitag 22 April 2011, 14:31:33 schrieb ragavender rao:
> yes.I too like that idea but people from some of the asian countries
> like china, japan may fing difficult. So english with addition of
> fewer languages can be used in it.
>
> On 4/22/11, Tomáš Chvátal <scarabeus@gentoo.org> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi,
> > I am quite getting annoyed by bugzilla attached outputs in various
> > interesting languages like Portugalese or French. I can read Russian so
> > that is at least bit ok :)
> >
> > I can understand that it might be nice to user to see these messages in
> > their native language, but it gets hell annoying when we have to figure
> > out wtf is going on with their build when they attach it to the bug.
> >
> > So I would like portage to filter/set environment the way it is always
> > English.
> >
> > Opinions?
> >
> > Cheers
> >
> > Tom
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.17 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >
> > iEYEARECAAYFAk2xZxIACgkQHB6c3gNBRYfPgwCeIFkMVFzVc1AuhSmG3cGJOw9O
> > Hk4AnRJtoDovwAfvGO6DdIGjCKEXvc3H
> > =7Mfc
> > -----END PGP SIGNATURE-----
--
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-22 17:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 11:31 [gentoo-dev] Disabling locale at emerge output Tomáš Chvátal
2011-04-22 12:31 ` ragavender rao
2011-04-22 17:53 ` Andreas K. Huettel [this message]
2011-04-24 16:48 ` Jeroen Roovers
2011-04-24 21:55 ` [gentoo-dev] " Duncan
2011-04-25 1:57 ` Jeroen Roovers
2011-04-25 5:24 ` Duncan
2011-04-25 4:05 ` Serkan Kaba
2011-04-25 6:14 ` Ulrich Mueller
2011-04-25 10:24 ` Jeroen Roovers
2011-04-25 13:40 ` ragavender rao
2011-04-22 12:37 ` [gentoo-dev] " Fabian Groffen
2011-04-22 12:57 ` Chí-Thanh Christopher Nguyễn
2011-04-26 2:06 ` [gentoo-dev] " Ryan Hill
2011-04-22 15:23 ` [gentoo-dev] " Jeroen Roovers
2011-04-22 17:50 ` Andreas K. Huettel
2011-04-22 15:40 ` Jeremy Olexa
2011-04-24 21:27 ` Andreas K. Huettel
2011-04-26 2:05 ` [gentoo-dev] " Ryan Hill
2011-04-26 4:02 ` Jeroen Roovers
2011-04-26 6:35 ` Michał Górny
2011-04-27 8:47 ` Ryan Hill
2011-04-27 16:26 ` Jeroen Roovers
2011-04-27 22:09 ` Chí-Thanh Christopher Nguyễn
2011-04-27 22:14 ` ross smith
2011-04-28 3:10 ` Ryan Hill
2011-04-28 12:00 ` Jeroen Roovers
2011-04-29 5:15 ` Ryan Hill
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=201104221953.36951.dilfridge@gentoo.org \
--to=dilfridge@gentoo.org \
--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