On Wed, 09 Oct 2024 17:25:13 +0200 I myself wrote: > ... > after a recent KDE upgrade among other new packages "emerge" also in- > stalled "dev-qt/qtwebengine" as a new dependency. Since on my five year > old laptop this package requires about 6 hours 20 minutes to build, I > decided to slightly redesign my package managing script and to use bina- > ry packages for long bilding dependencies I build with default USE flags > anyway. > > It works, but is there a way (short of using "|grep -v ...") to prevent > "emerge" from spitting plenty of noisy but rather irrelevant progress > messages to standard output (which it also logs to "/var/log/emerge- > fetch.log")?
I meanwhile learned two things: 1. Running "emerge --ask ... | grep -v ..." does't work nicely, because after "emerge" has produced its output it doesn't immediately close its output stream, while "grep" waits for more input to fill its in- ternal buffer. So the pipe stalls without asking whether or not to continue and one has to blindly type "y" or "n". 2. By accidentally running an unrelated "wget" command without option "--quiet" I realized that these noisy progress messages most probably originate from a call to "wget" issued by "emerge" directly. So I appended the line "quiet = on" to file "/etc/wgetrc" and that real- ly suppressed all these progress messages. The only question remaining now is whether "emerge" calling "wget" without "--quiet" option is a bug or a feature. Opinions? Sincerely, Rainer
