On Wednesday 24 May 2006 07:42, Jakub Moc wrote:
> Please, make portage spit out the errors in English by *default* to not
> waste people's time. If someone insists on overriding it, then let them
> do it in make.conf
and where do you propose we document said override ? in the locale guide ?
th
On Wednesday 24 May 2006 07:42, Jakub Moc wrote:
> Every other user that is asked to provide the messages with locales set
> to C comes back asking how do I do it. Then they come back saying, oh
> LC_ALL=C, or LC_MESSAGES=C didn't work, where do I put it exactly? Then
> they come back and say, oh,
On Wed, 24 May 2006 13:42:37 +0200
Jakub Moc <[EMAIL PROTECTED]> wrote:
> Please, make portage spit out the errors in English by *default* to
> not waste people's time. If someone insists on overriding it, then
> let them do it in make.conf, but the default should be English and
> English should b
On Wed, 24 May 2006 13:17:54 +0200
Harald van Dijk <[EMAIL PROTECTED]> wrote:
> LINGUAS is not Gentoo-specific at all. Gentoo didn't even come up with
> it. It's a gettext variable, which is re-used (with an annoyingly
> slightly different meaning) by Gentoo.
Thanks for the clarification - I only
Kevin F. Quinn wrote:
> On Fri, 19 May 2006 11:38:06 +0200
> Stefan Schweizer <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> there are at least two problems with how portage currently handles
>> locales:
>>
>> - Firstly some packages fail to build with obscure LC_* settings
>
> Anything that expects o
On Wed, May 24, 2006 at 12:36:17PM +0200, Kevin F. Quinn wrote:
> On Fri, 19 May 2006 11:38:06 +0200
> Stefan Schweizer <[EMAIL PROTECTED]> wrote:
> > One problem could be that packages depend on LC_* to install the
> > correct language. But that is a real bug then in my opinion, because
> > ebuild
On Fri, 19 May 2006 11:38:06 +0200
Stefan Schweizer <[EMAIL PROTECTED]> wrote:
> Hi,
>
> there are at least two problems with how portage currently handles
> locales:
>
> - Firstly some packages fail to build with obscure LC_* settings
Anything that expects ordering etc from a particular locale
On Friday 19 May 2006 05:38, Stefan Schweizer wrote:
> I propose to have the portage build environment set the language to English
> or LC_ALL=C by default. That would significantly reduce the bugs with
> unreadable error messages+ solve all the et_EE bugs at once.
this is complete garbage
you're
On Friday 19 May 2006 15:24, Harald van Dijk wrote:
> grep through gcc/po/*, which doesn't require installation of the
> locales
Providing the error messages in english is part of what I consider the users
job when filing a bug report. Having to grep for the strings is wasted time.
I'm not so sur
On Fri, May 19, 2006 at 02:44:03PM +0100, Daniel Drake wrote:
> Harald van Dijk wrote:
> >and as for
> >unreadable error messages, getting German gcc output in a German locale
> >is a feature, not a bug.
>
> I agree - but only when you use gcc on the command line, or in a
> Makefile, or in some o
Harald van Dijk wrote:
and as for
unreadable error messages, getting German gcc output in a German locale
is a feature, not a bug.
I agree - but only when you use gcc on the command line, or in a
Makefile, or in some other normal usage scenario.
I think Stefan is suggesting just using the st
On Fri, May 19, 2006 at 09:09:08AM -0400, Patrick McLean wrote:
> > No, it's needlessly unfriendly to users, and encourages broken packages.
> > et_EE breakage should be fixed, and slowly but surely is, and as for
> > unreadable error messages, getting German gcc output in a German locale
> > is a
> No, it's needlessly unfriendly to users, and encourages broken packages.
> et_EE breakage should be fixed, and slowly but surely is, and as for
> unreadable error messages, getting German gcc output in a German locale
> is a feature, not a bug. It can indeed be a problem in bugreports, but
> it's
Harald van Dijk wrote:
> is a feature, not a bug. It can indeed be a problem in bugreports, but
> it's a much milder one, since it's trivial to look up what any
> particular message is translated from.
Well no, I completely disagree. Error output in $random language makes
searching for duplicate b
On Fri, May 19, 2006 at 11:38:06AM +0200, Stefan Schweizer wrote:
> Hi,
>
> there are at least two problems with how portage currently handles locales:
>
> - Firstly some packages fail to build with obscure LC_* settings
> The continuous stream of et_EE bugs is annoying: http://tinyurl.com/jsqzb
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?
Otoh LC_ALL=
16 matches
Mail list logo
