From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: Gentoo-User@Lists.Gentoo.Org
Subject: [gentoo-user] Suppressing some "emerge" output
Date: Wed, 09 Oct 2024 17:25:13 +0200 [thread overview]
Message-ID: <6706a05b.050a0220.29bc49.7bc5@mx.google.com> (raw)
Greetings,
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")? Since I want to save the "emerge" logs and since "man e-
merge" is less than helpful with respect to option "--quiet" ("Results
may vary, but the general outcome is a reduced or condensed output from
portage's displays.") I have yet hesitated to enable this option. Would
it help at all? Would "emerge" still write logs to "/var/log/portage/
*/*" and "/var/log/emerge.log"? Is there another option or "FEATURE"
setting I should use?
Any suggestions welcome :-)
Sincerely,
Rainer
reply other threads:[~2024-10-09 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6706a05b.050a0220.29bc49.7bc5@mx.google.com \
--to=rainer.woitok@gmail.com \
--cc=Gentoo-User@Lists.Gentoo.Org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox