From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Stopping some emerges from being recorded in the logs.
Date: Sun, 20 Jul 2025 04:24:48 -0500 [thread overview]
Message-ID: <c75777c3-f476-14f1-1c1b-6132ae2601fa@gmail.com> (raw)
In-Reply-To: <1912b643-59ef-14bd-1b50-32d461385ab6@gmail.com>
Dale wrote:
> Howdy,
>
> I do my updates in a chroot. When it is done in the chroot, I copy the
> packages over to my main OS and install with -k and it keeps my running
> OS more stable. There is one problem tho. When I do that, the emerge
> times for installing the packages with -k, which is a LOT faster, are
> also recorded in the emerge.log file. When I use genlop -c to see how
> much longer a compile is going to take, it makes the results of genlop
> way off. A package that may take a hour to compile can install as a
> binary in a couple minutes. Poor genlop gets confused. Did the emerge
> take a couple minutes or a hour?
>
> Is there a way that I can stop emerge from logging the package installs
> with -k? Some little known option?
>
> I also thought about copying the emerge.log file over from the chroot
> after I complete the -k update on my main install. Not logging the -k
> update would be the same result. Thing is, I forget to do it. It would
> be nice if I could use a emerge option but does anyone see a problem
> with this way?
>
> Dale
>
> :-) :-)
>
> P. S. Got my tractor back together and even bladed a driveway this
> morning. It's doing a LOT better but I want to rebuild the other side
> pretty soon. No leaks and no parts left over.
>
The only way I've come up with to work around this, copy the emerge log
file over after I do my emerge -k on my main OS, if I don't forget. I
wish I could just tell emerge not to log emerge -k at all.
Dale
:-) :-)
prev parent reply other threads:[~2025-07-20 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 2:13 [gentoo-user] Stopping some emerges from being recorded in the logs Dale
2025-07-20 9:24 ` Dale [this message]
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=c75777c3-f476-14f1-1c1b-6132ae2601fa@gmail.com \
--to=rdalek1967@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