| 1 |
On Sat, Nov 12, 2011 at 9:40 PM, Mike Frysinger <vapier@g.o> wrote: |
| 2 |
> On Saturday 12 November 2011 17:24:08 Patrick Lauer wrote: |
| 3 |
>> On 11/11/11 16:44, Zac Medico wrote: |
| 4 |
>> >> good point. we don't want to punish old portage users. let's enable it |
| 5 |
>> >> by default in portage itself then. just add `elog` output to the |
| 6 |
>> >> portage ebuild to inform users of the change ? or do we want a news |
| 7 |
>> >> item ? |
| 8 |
>> >> |
| 9 |
>> >> what's the flag to negate the default ? --no-quiet-build ? ;) |
| 10 |
>> > |
| 11 |
>> > It's --quiet-build=n. I've gone ahead and enabled it for release in |
| 12 |
>> > portage-2.1.10.34: |
| 13 |
>> > |
| 14 |
>> > http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0cc1 |
| 15 |
>> > 74b6fc28feb26ea151d76f794e0ff2c2fa39 |
| 16 |
>> |
| 17 |
>> Lots of people in #gentoo are unhappy with it. |
| 18 |
> |
| 19 |
> most changes people will be unhappy with because it's different |
| 20 |
> |
| 21 |
>> Most devs will be unhappy as it makes it harder to view the log while |
| 22 |
>> building. |
| 23 |
> |
| 24 |
> devs are not the normal case. it's trivial to have them use --quiet-build=n |
| 25 |
> in their default emerge opts. |
| 26 |
|
| 27 |
Then why not you and the other 2 guys that approved this change here |
| 28 |
(and are the only people I saw approving this, TBH), add |
| 29 |
--quiet-build=y to your default emerge opts and avoid this kind of |
| 30 |
change? |
| 31 |
|
| 32 |
Regards, |
| 33 |
|
| 34 |
-- |
| 35 |
Rafael Goncalves Martins |
| 36 |
Gentoo Linux developer |
| 37 |
http://rafaelmartins.eng.br/ |
Archives