| 1 |
On Sun, Dec 4, 2011 at 6:17 AM, Thomas Sachau <tommy@g.o> wrote: |
| 2 |
> 2. Should the default output of portage be changed to quiet? |
| 3 |
> |
| 4 |
> If yes, is a simple portage message for 2.1.* users enough to inform |
| 5 |
> users about this highly visible change? Especially in the context in |
| 6 |
> mind, that a good amount of packages have elog messages, so it is pretty |
| 7 |
> easy to miss this hint for a change in portage behaviour. |
| 8 |
|
| 9 |
I'm already planning to send out a GLEP 42 news item for this before it |
| 10 |
goes to stable. It will include a description of --quiet-build behavior |
| 11 |
(including automatic display of build output when a build fails), how to |
| 12 |
use EMERGE_DEFAULT_OPTS to customize the local default, and how the |
| 13 |
default PORTAGE_ELOG_SYSTEM/PORTAGE_ELOG_CLASSES settings ensure that |
| 14 |
elog messages are displayed regardless of the --quiet-build setting. |
| 15 |
-- |
| 16 |
Thanks, |
| 17 |
Zac |
Archives