public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Build log locales
Date: Tue, 6 Aug 2013 15:05:49 -0400	[thread overview]
Message-ID: <CAGfcS_mnUFR+M40P45pujRgu0oEgaX0BQkGzXptE9rH=7yca+Q@mail.gmail.com> (raw)
In-Reply-To: <CAJ0EP413Rz7z_2kURJ=WwyueA2DC9jkzkwgGDiu8TPKZoRn_3A@mail.gmail.com>

On Tue, Aug 6, 2013 at 2:35 PM, Mike Gilbert <floppym@gentoo.org> wrote:
> On Tue, Aug 6, 2013 at 12:07 PM, Ulrich Mueller <ulm@gentoo.org> wrote:
>>>>>>> On Tue, 6 Aug 2013, Andreas K Huettel wrote:
>>> [...] I consider any build system that fails depending on locale as
>>> br0ken and in need of fixing.
>>
>> +1
>>
>
> You are welcome to waste your time fixing python setup.py files and
> unit tests that are broken unless you have a UTF-8 locale set. I think
> there are better uses of our time.
>

I think we're drifting topic-wise.  The main concern is about bug
reports written in languages other than english that may be difficult
for most developers to read, and not so much about build-system
compatibility with locale settings.  Sure, they should support
everything, but it isn't a critical bug if they don't.

My personal feeling on this is that maintainers should not be required
to accept bugs that contain logs generally written in something other
than English.  They may still accept them at their own discretion.

I'm also fine with default portage configurations that support logs in
English by default even when the system locale is not set this way, as
long as users have a way to override the setting.

Rich


  reply	other threads:[~2013-08-06 19:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  9:41 [gentoo-project] Call for agenda items - Council meeting 2013-08-13 Ulrich Mueller
2013-08-01  0:36 ` William Hubbs
2013-08-01 20:04   ` Alexis Ballier
2013-08-01 21:07     ` William Hubbs
2013-08-01 21:40       ` Alexis Ballier
2013-08-06 14:13 ` Build log locales (was: [gentoo-project] Call for agenda items - Council meeting 2013-08-13) Andreas K. Huettel
2013-08-06 15:39   ` [gentoo-project] Re: Build log locales Michael Weber
2013-08-06 15:52   ` Build log locales (was: [gentoo-project] Call for agenda items - Council meeting 2013-08-13) Michał Górny
2013-08-06 19:34     ` Alexis Ballier
2013-08-07  0:24       ` Mike Gilbert
2013-08-07  9:38         ` Andreas K. Huettel
2013-08-07 10:08           ` [gentoo-project] Re: Build log locales Ulrich Mueller
2013-08-07 10:14             ` Andreas K. Huettel
2013-08-06 16:07   ` Ulrich Mueller
2013-08-06 18:35     ` Mike Gilbert
2013-08-06 19:05       ` Rich Freeman [this message]
2013-08-06 19:26       ` Ulrich Mueller
2013-08-06 19:31       ` Michał Górny
2013-08-07  0:13         ` Mike Gilbert
2013-08-07  9:24 ` [gentoo-project] Council meeting: Tuesday 2013-08-13, 19:00 UTC Ulrich Mueller

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='CAGfcS_mnUFR+M40P45pujRgu0oEgaX0BQkGzXptE9rH=7yca+Q@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-project@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