| 1 |
On 11/10/2011 05:56 PM, Mike Frysinger wrote: |
| 2 |
> On Thursday 10 November 2011 20:39:11 Mike Frysinger wrote: |
| 3 |
>> On Thursday 10 November 2011 19:09:28 Luca Barbato wrote: |
| 4 |
>>> On 11/5/11 1:58 AM, Kacper Kowalik wrote: |
| 5 |
>>>> I'd like to ask that we enable verbose building by default. I have |
| 6 |
>>>> cmake-utils.eclass in mind, because it's dead easy there, but there's a |
| 7 |
>>>> lot of packages that support things like "make V=1" or "make VERBOSE=1" |
| 8 |
>>>> too. |
| 9 |
>>>> |
| 10 |
>>>> I've seen too many bugs reports today that gave me cute, colorful |
| 11 |
>>>> build.logs and almost no information about underlaying bug... |
| 12 |
>>> |
| 13 |
>>> That could be done, but I'd advise to make sure our users know that the |
| 14 |
>>> could have a quiet/silent output from portage. |
| 15 |
>> |
| 16 |
>> if you want quiet portage output, use something like --quiet when running |
| 17 |
>> emerge. the verbosity of the build output isn't really an issue imo. |
| 18 |
> |
| 19 |
> perhaps a more controversial question: should we make --quiet the default ? |
| 20 |
> -mike |
| 21 |
|
| 22 |
I think --quiet-build would be a reasonable default, but --quiet |
| 23 |
suppresses various warning messages that I think need to be enabled by |
| 24 |
default for newbies. |
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives