Re: LC_MESSAGES=C in debian/rules
- To: email@example.com
- Subject: Re: LC_MESSAGES=C in debian/rules
- From: Goswin von Brederlow <firstname.lastname@example.org>
- Date: Wed, 04 May 2011 13:09:15 +0200
- Message-id: <[🔎] email@example.com>
- In-reply-to: <20110429095142.GA1893@angband.pl> (Adam Borowski's message of "Fri, 29 Apr 2011 11:51:43 +0200")
- References: <4DBA7649.firstname.lastname@example.org> <20110429084804.GC23548@pcpool00.mathematik.uni-freiburg.de> <20110429095142.GA1893@angband.pl>
Adam Borowski <email@example.com> writes:
> On Fri, Apr 29, 2011 at 10:48:04AM +0200, Bernhard R. Link wrote:
>> * Daniel Stender <firstname.lastname@example.org> [110429 10:37]:
>> > is it best practice to set LC_MESSAGE=C in debian/rules to prevent
>> > things like test suite breaking when building within non-English
>> > locales?
>> If you want to set something, set LC_ALL.
>> Otherwise a user-set LC_ALL will override it.
>> (and it also sets LC_CTYPE, which is even more likely to cause
>> problems than LC_MESSAGES).
> Explanation: the order env vars are checked is:
> 1. LC_ALL
> 2. LC_$category
> 3. LANG
Or run your test suite with env -i.