View previous topic :: View next topic |
Show or hide build output by default? |
emerge should hide build output by default (unless --quiet-build=n) |
|
28% |
[ 135 ] |
emerge should show build output by default (unless --quiet-build=y) |
|
51% |
[ 240 ] |
The -v option should control whether build output is shown or not by default |
|
17% |
[ 81 ] |
Other (please comment) |
|
2% |
[ 10 ] |
|
Total Votes : 466 |
|
Author |
Message |
rogerx Tux's lil' helper
Joined: 06 Apr 2004 Posts: 118
|
|
Back to top |
|
|
zmedico Developer
Joined: 02 Jan 2004 Posts: 352 Location: California USA
|
Posted: Fri Dec 02, 2011 4:55 pm Post subject: |
|
|
In order to help avoid confusion, I'm going to send out a GLEP 42 news item before the --quiet-build default goes to stable. _________________ Zac |
|
Back to top |
|
|
perlovka n00b
Joined: 04 Aug 2004 Posts: 16 Location: Israel
|
Posted: Sat Dec 03, 2011 8:29 am Post subject: |
|
|
with quiet build enabled, you can't see the download progress for big files, because wget outputs nothing to emerge-fetch.log |
|
Back to top |
|
|
zmedico Developer
Joined: 02 Jan 2004 Posts: 352 Location: California USA
|
Posted: Sat Dec 03, 2011 9:23 am Post subject: |
|
|
perlovka wrote: | with quiet build enabled, you can't see the download progress for big files, because wget outputs nothing to emerge-fetch.log |
Bug 391323 is about adding additional information like fetch progress to --quiet-build output (possibly controlled by separate options).
Note that emerge-fetch.log is only used for prefetch which is enabled by FEATURES=parallel-fetch. Normal fetches output to individual build logs for each ebuild, rather than emerge-fetch.log. This allows multiple ebuild fetchers to write to separate logs concurrently for --jobs. _________________ Zac |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Sat Jan 14, 2012 2:49 am Post subject: |
|
|
I found this after reading a vague reference to the quiet build option today so I thought I would update anyone who didn't know.
Quote: |
Quiet build default in Portage
==============================
Discuss/vote: Should the quiet default get reverted before affected
Portage versions get stabilised? [2]
The Council agreed that quiet-build behaviour of Portage should be made
an opt-in for existing installs (chainsaw, jmbsvicetto, grobian). The
suggested implementation for this is by reverting the default of
quiet-build.
Indifferent to the value of this default for existing installs:
dberkholz, ulm, betelgeuse.
The Council agreed that quiet-build behaviour of Portage can be made the
default for new installs (dberkholz, betelgeuse, jmbsvicetto, chainsaw,
grobian). A possible implementation for this suggested by jmbsvicetto
is via the stage building process (catalyst) to enable quiet-build in
the produced make.conf.
Indifferent to the value of this default for new installs: ulm.
The Council likes to note that the quiet-build option in itself seems
unknown to many, and hence leads to people searching for long how to
change it. Some pointers to documentation may be necessary. As
understood, a GLEP 42 news item is already planned. Another way of
getting it better documented would be to add it commented out to
make.conf.
|
From http://www.gentoo.org/proj/en/council/meeting-logs/20111213-summary.txt _________________ #gentoo-kde on freenode |
|
Back to top |
|
|
rogerx Tux's lil' helper
Joined: 06 Apr 2004 Posts: 118
|
Posted: Wed Feb 08, 2012 5:10 am Post subject: |
|
|
Hey all. I just had my laptop do it's tri-montly "eix-sync && emerge -uDNq world", and found the output just fabulous.
The output shows 95 (binary prebuilt) packages (from my main host) all install successfully and quietly with the additional "important notices" (ie. einfo) data afterwards.
Of course, I read every einfo statement. ;-)
Main point being, everything looks good without any unneeded data and I usually perform more routine updates here on my hosts and clients.
Cheers! _________________ Roger
http://rogerx.freeshell.org/ |
|
Back to top |
|
|
Zentoo Apprentice
Joined: 18 Nov 2002 Posts: 195 Location: /dev/console
|
Posted: Wed Mar 07, 2012 9:56 am Post subject: |
|
|
Hi !
I vote to hide build info by default but I think we should control it by a FEATURE in make.conf to control the default state (y/n) and not to have to use --quiet-build=X for people that don't use the default.
Actually i use the quietemerge script for the hide default behaviour:
http://code.google.com/p/quietemerge/ _________________ Kernel 5.14.15-zen | Gcc 11.2 | Glibc 2.34
Core i7 6700K @ 4.6GHz | 32Gb
ACCEPT_KEYWORDS="~amd64"
CFLAGS="-march=native -O2 -pipe" |
|
Back to top |
|
|
dalek Veteran
Joined: 19 Sep 2003 Posts: 1353 Location: Mississippi USA
|
Posted: Thu Mar 08, 2012 12:52 am Post subject: |
|
|
Zentoo wrote: | Hi !
I vote to hide build info by default but I think we should control it by a FEATURE in make.conf to control the default state (y/n) and not to have to use --quiet-build=X for people that don't use the default.
Actually i use the quietemerge script for the hide default behaviour:
http://code.google.com/p/quietemerge/ |
In make.conf:
Code: | EMERGE_DEFAULT_OPTS="--quiet-build=n" |
If you already use that line, just add it to the rest of the options. You can set it to y or n whichever is your choice.
_________________ My rig: Gigabyte GA-970A-UD3P mobo, AMD FX-8350 Eight-Core CPU, ZALMAN CNPS10X Performa CPU cooler,
G.SKILL 32GB DDR3 PC3 12800 Memory Nvidia GTX-650 video card LG W2253 Monitor
60TBs of hard drive space using LVM
Cooler Master HAF-932 Case |
|
Back to top |
|
|
|