| 1 |
On Saturday 12 November 2011 17:24:08 Patrick Lauer wrote: |
| 2 |
> On 11/11/11 16:44, Zac Medico wrote: |
| 3 |
> >> good point. we don't want to punish old portage users. let's enable it |
| 4 |
> >> by default in portage itself then. just add `elog` output to the |
| 5 |
> >> portage ebuild to inform users of the change ? or do we want a news |
| 6 |
> >> item ? |
| 7 |
> >> |
| 8 |
> >> what's the flag to negate the default ? --no-quiet-build ? ;) |
| 9 |
> > |
| 10 |
> > It's --quiet-build=n. I've gone ahead and enabled it for release in |
| 11 |
> > portage-2.1.10.34: |
| 12 |
> > |
| 13 |
> > http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=0cc1 |
| 14 |
> > 74b6fc28feb26ea151d76f794e0ff2c2fa39 |
| 15 |
> |
| 16 |
> Lots of people in #gentoo are unhappy with it. |
| 17 |
|
| 18 |
most changes people will be unhappy with because it's different |
| 19 |
|
| 20 |
> Most devs will be unhappy as it makes it harder to view the log while |
| 21 |
> building. |
| 22 |
|
| 23 |
devs are not the normal case. it's trivial to have them use --quiet-build=n |
| 24 |
in their default emerge opts. |
| 25 |
-mike |
Archives