public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Disabling locale at emerge output
Date: Mon, 25 Apr 2011 05:24:37 +0000 (UTC)	[thread overview]
Message-ID: <pan.2011.04.25.05.24.37@cox.net> (raw)
In-Reply-To: 20110425035730.608d531e@epia.jer-c2.orkz.net

Jeroen Roovers posted on Mon, 25 Apr 2011 03:57:30 +0200 as excerpted:

> In my opinion, what we should do instead is acknowledge the policy
> that's been in place all along, that is to require build logs with
> "universally" appreciated error messages, and reinforce that policy
> using technical means, instead of having asking users nicely every time
> for something they may not even be aware of.

I've no problem with that, as long as is traditional with Gentoo, we give 
users a clear override, should they have reason to believe the want/need 
it.

I'd also have no problem with closing bugs as NEEDINFO if they file with 
non-English errors and the like, regardless of whether any additional 
technical measures to ensure English errors by default are taken.  Even in 
the event of real-locale-bug exceptions such as locale dependent alphanum 
ordering bugs, I'd say an entirely proper gentoo resolution is UPSTREAM.

So you see I much more agree with you than disagree.  I'm simply saying, 
let there be an override if the user insists, just as Gentoo normally lets 
the user override pretty much anything, if they insist.  As long as that 
override is there to be used if necessary, go for it!

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2011-04-25  5:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 11:31 [gentoo-dev] Disabling locale at emerge output Tomáš Chvátal
2011-04-22 12:31 ` ragavender rao
2011-04-22 17:53   ` Andreas K. Huettel
2011-04-24 16:48     ` Jeroen Roovers
2011-04-24 21:55       ` [gentoo-dev] " Duncan
2011-04-25  1:57         ` Jeroen Roovers
2011-04-25  5:24           ` Duncan [this message]
2011-04-25  4:05         ` Serkan Kaba
2011-04-25  6:14           ` Ulrich Mueller
2011-04-25 10:24             ` Jeroen Roovers
2011-04-25 13:40               ` ragavender rao
2011-04-22 12:37 ` [gentoo-dev] " Fabian Groffen
2011-04-22 12:57 ` Chí-Thanh Christopher Nguyễn
2011-04-26  2:06   ` [gentoo-dev] " Ryan Hill
2011-04-22 15:23 ` [gentoo-dev] " Jeroen Roovers
2011-04-22 17:50   ` Andreas K. Huettel
2011-04-22 15:40 ` Jeremy Olexa
2011-04-24 21:27 ` Andreas K. Huettel
2011-04-26  2:05 ` [gentoo-dev] " Ryan Hill
2011-04-26  4:02   ` Jeroen Roovers
2011-04-26  6:35     ` Michał Górny
2011-04-27  8:47     ` Ryan Hill
2011-04-27 16:26       ` Jeroen Roovers
2011-04-27 22:09         ` Chí-Thanh Christopher Nguyễn
2011-04-27 22:14           ` ross smith
2011-04-28  3:10         ` Ryan Hill
2011-04-28 12:00           ` Jeroen Roovers
2011-04-29  5:15             ` Ryan Hill

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=pan.2011.04.25.05.24.37@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@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