Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
On Sunday 04 December 2011 06:58:06 Chí-Thanh Christopher Nguyễn wrote:
> Mike Frysinger schrieb:
> > and in reality, you're complaining only about LC_MESSAGES, not LC_ALL or
> > any other locale category ...
>
> I too think it is sufficient to have
> LC_MESSAGES=C
> in the default make.conf (or somewhere else where the user can easily
> change it), with a comment to leave it like this for build.log when
> reporting bugs.
this would allow a small # of bugs to creep into our system (some packages run
programs and then grep the output for english strings and miss setting
LC_{MESSAGES,ALL} to C first), but that might easily be smaller than the burden
placed on bug-wranglers ...
i'm indifferent to setting LC_MESSAGES=C in the default make.conf (i.e. via
catalyst). i don't think it should be in the profile's make.defaults.
-mike
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
On 12/04/2011 03:58 AM, Chí-Thanh Christopher Nguyễn wrote: > Mike Frysinger schrieb: >> and in reality, you're complaining only about LC_MESSAGES, not LC_ALL or any >> other locale category ... > > I too think it is sufficient to have > LC_MESSAGES=C > in the default make.conf (or somewhere else where the user can easily > change it), with a comment to leave it like this for build.log when > reporting bugs. If we want it to go in the default make.conf, it would go in catalyst, since that's what generates the default make.conf for stage builds. We can get an equivalent result by putting it in make.defaults of the base profile, and adding a note to the handbook and/or localization guide. -- Thanks, Zac
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
On Sunday 04 December 2011 12:37:15 James Cloos wrote: > As someone who leaves root w/o LANG, I would note that there are a few > packages which cannot build unless LANG is set to a UTF-8 locale. file a bug then > What we really need is C.UTF-8 and/or POSIX.UTF-8, and to force *that* > in emerge(1), ebuild(1), etc. no. it'll break systems that don't have UTF8 support. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
As someone who leaves root w/o LANG, I would note that there are a few packages which cannot build unless LANG is set to a UTF-8 locale. What we really need is C.UTF-8 and/or POSIX.UTF-8, and to force *that* in emerge(1), ebuild(1), etc. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
On 12/4/11 12:58 PM, Chí-Thanh Christopher Nguyễn wrote: > Mike Frysinger schrieb: >> and in reality, you're complaining only about LC_MESSAGES, not LC_ALL or any >> other locale category ... > > I too think it is sufficient to have > LC_MESSAGES=C > in the default make.conf (or somewhere else where the user can easily > change it), with a comment to leave it like this for build.log when > reporting bugs. Sounds like a good idea - it's a good default, allows the user to change it, and to easily use a different locale for non-portage interactions. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
2011/12/4 Chí-Thanh Christopher Nguyễn : > I too think it is sufficient to have > LC_MESSAGES=C > in the default make.conf (or somewhere else where the user can easily > change it), with a comment to leave it like this for build.log when > reporting bugs. ++ Or if that goes too far have it commented out but still in the file - so that users can just remove one character to implement it. This would need to be accompanied by instructions in Bugzilla so that the wranglers don't need to post them over and over again. Users should be able to work in their native languages on their own PCs (Gentoo is about choice) - the key is just to try to prevent these kinds of issues in the first place. We already have notes about attaching build.log - all we need to do is include the words "with LC_MESSAGES=C to ensure logs are in English" in the note. Rich
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
Mike Frysinger schrieb: > and in reality, you're complaining only about LC_MESSAGES, not LC_ALL or any > other locale category ... I too think it is sufficient to have LC_MESSAGES=C in the default make.conf (or somewhere else where the user can easily change it), with a comment to leave it like this for build.log when reporting bugs. Best regards, Chí-Thanh Christopher Nguyễn
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
On Sun, 4 Dec 2011 04:50:00 +0100 Jeroen Roovers wrote: > Subject says it all. More and more bug attachments appear that have > been generated with non-English locales, and it's a nuisance for both > bug reporters and bug wranglers to request/provide the sane > alternative that every developer should be able to read. Will break random packages with stable Python 3.1, and current testing Python 3.x versions. -- Best regards, Michał Górny signature.asc Description: PGP signature
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
On Saturday 03 December 2011 22:50:00 Jeroen Roovers wrote: > Subject says it all. More and more bug attachments appear that have > been generated with non-English locales, and it's a nuisance for both > bug reporters and bug wranglers to request/provide the sane alternative > that every developer should be able to read. non C locales triggers real bugs i think we should be fixing and in reality, you're complaining only about LC_MESSAGES, not LC_ALL or any other locale category ... -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
On Sat, Dec 3, 2011 at 7:50 PM, Jeroen Roovers wrote: > Subject says it all. More and more bug attachments appear that have > been generated with non-English locales, and it's a nuisance for both > bug reporters and bug wranglers to request/provide the sane alternative > that every developer should be able to read. I think forcing LC_ALL=C is crazy. -A > > > jer >
[gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?
Subject says it all. More and more bug attachments appear that have been generated with non-English locales, and it's a nuisance for both bug reporters and bug wranglers to request/provide the sane alternative that every developer should be able to read. jer
