Re: [gentoo-dev] Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?

On Sun, Dec 4, 2011 at 1:51 AM, Ryan Hill wrote: > 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 requ

Re: [gentoo-dev] Re: So now that we have --quiet-build as default, can we talk about a forced LC_ALL=C again?

On Sun, 4 Dec 2011 00:51:17 -0600 Ryan Hill wrote: > How many times have you needed to request build logs in english since > the last time you brought this up? How many times have you had to > request emerge --info or build logs in general? Many dozens of times, and a magnitude more dozens of t

[gentoo-dev] Re: 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 sh

Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?

On Sat, 3 Dec 2011 22:14:16 -0800 Alec Warner wrote: > Can we just translate the error messages? *I* sure can but it takes time and effort, and for ever developer who looks at this, the process is repeated unless bug wranglers or other handy users happen to provide the translation. Just think

Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?

On Sat, Dec 3, 2011 at 10:03 PM, Jeroen Roovers wrote: > On Sun, 4 Dec 2011 00:21:42 -0500 > Mike Frysinger wrote: > >> and in reality, you're complaining only about LC_MESSAGES, not LC_ALL >> or any other locale category ... > > Fine. Can we just translate the error messages? -A > > >     je

Re: [gentoo-dev] So now that we have --quiet-build as default, can we talk about a forced LC_MESSAGES=C again?

On Sun, 4 Dec 2011 00:21:42 -0500 Mike Frysinger wrote: > and in reality, you're complaining only about LC_MESSAGES, not LC_ALL > or any other locale category ... Fine. jer

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

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 shoul

[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

Re: [gentoo-dev] user management mitigation

Mike, can you offer a tip on how to "trivially hook into whatever craziness" with the help of user.eclass? My goal is to have regular enewuser and enewgroup work for ROOT=/xyz. But I don't currently have a clue what would *not* be a horribly broken way to do this. It seems like I perhaps should