| 1 |
On 11/10/2011 07:17 PM, Zac Medico wrote: |
| 2 |
> On 11/10/2011 06:59 PM, Mike Frysinger wrote: |
| 3 |
>> On Thursday 10 November 2011 21:11:38 Zac Medico wrote: |
| 4 |
>>> On 11/10/2011 05:56 PM, Mike Frysinger wrote: |
| 5 |
>>>> On Thursday 10 November 2011 20:39:11 Mike Frysinger wrote: |
| 6 |
>>>>> if you want quiet portage output, use something like --quiet when |
| 7 |
>>>>> running emerge. the verbosity of the build output isn't really an |
| 8 |
>>>>> issue imo. |
| 9 |
>>>> |
| 10 |
>>>> perhaps a more controversial question: should we make --quiet the default |
| 11 |
>>> |
| 12 |
>>> I think --quiet-build would be a reasonable default, but --quiet |
| 13 |
>>> suppresses various warning messages that I think need to be enabled by |
| 14 |
>>> default for newbies. |
| 15 |
>> |
| 16 |
>> WFM |
| 17 |
>> |
| 18 |
>> would putting this as EMERGE_DEFAULT_OPTS in profiles/base/make.defaults be too |
| 19 |
>> hideous for people to swallow ? |
| 20 |
>> -mike |
| 21 |
> |
| 22 |
> Less than sys-apps/portage-2.1.9.43 will choke on that, it's an |
| 23 |
> unrecognized option. So, we'd better just enable it by default for the |
| 24 |
> next portage release. |
| 25 |
|
| 26 |
Actually, it's been around since portage-2.1.7.5 (bug #291200). Still, |
| 27 |
it's probably better not to set it in the profile. |
| 28 |
-- |
| 29 |
Thanks, |
| 30 |
Zac |
Archives