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: Sun, 24 Apr 2011 21:55:13 +0000 (UTC)	[thread overview]
Message-ID: <pan.2011.04.24.21.55.13@cox.net> (raw)
In-Reply-To: 20110424184853.3312c774@epia.jer-c2.orkz.net

Jeroen Roovers posted on Sun, 24 Apr 2011 18:48:53 +0200 as excerpted:

> On Fri, 22 Apr 2011 19:53:36 +0200 "Andreas K. Huettel"
> <dilfridge@gentoo.org> wrote:
> 
> 
>> How about a portage "feature" that is off by default? Like, "locale"
>> meaning "build with locale"?
> 
> You mean we should settle for only slightly improved odds of getting a
> build log we all can read?

The odds should be /vastly/ improved.

1)  FEATURES=locale would be off by default, so portage would build with 
POSIX locale by default.

2) The feature description could suitably strongly discourage turning it 
on if one plans to file bugs at all, and/or turning it off to file those 
bugs (thus further discouraging turning it on in the first place).

3) Can features be masked in the profiles?  If so, mask the feature if 
felt necessary, requiring jumping thru even more MORE hoops to turn it on, 
thus discouraging it even further.

But regardless of the fact that I only personally do English, I do believe 
the option should remain for those who wish to change it, to do so, 
regardless of how strongly discouraged said option might be.  (Funny, I 
never thought I'd be taking /this/ side of such an argument! =;^0 )

-- 
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-24 21:56 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       ` Duncan [this message]
2011-04-25  1:57         ` [gentoo-dev] " Jeroen Roovers
2011-04-25  5:24           ` Duncan
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.24.21.55.13@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