Howdy,

I have a chroot environment that I do updates in.  Once the updates are
done, I copy the binaries and distfiles over to my running system and
use the -k option to update everything in my real system.  It comes in
real handy when libreoffice, Firefox, qtwebengine and other large time consuming packages are being updated.  The bad thing is, I have the full length of build time in the chroot but the binary install on my running system.  Is there a way to either stop it from logging binary updates or removing them after it is done?  I'd rather it not keep those times in
either place really.  I can't find a emerge option.  It seems to record everything regardless.  My reason for this, the binary install times
throws off genlop -c and its estimates. 

Anybody have ideas? 

Thanks.

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dale schrieb am 06.03.22 um 06:53:

I have a chroot environment that I do updates in.  Once the updates are done, I copy the binaries and distfiles over to my running system and
use the -k option to update everything in my real system.  It comes in
real handy when libreoffice, Firefox, qtwebengine and other large time consuming packages are being updated.  The bad thing is, I have the full length of build time in the chroot but the binary install on my running system.  Is there a way to either stop it from logging binary updates or removing them after it is done?  I'd rather it not keep those times in either place really.  I can't find a emerge option.  It seems to record everything regardless.  My reason for this, the binary install times
throws off genlop -c and its estimates.

Anybody have ideas?

There is a long-standing bug [1] regrading this issue but given genlop currently is not actively developed I don't think there will be a
solution soon. It should be possible to exclude binary merges as they
can be identified in emerge.log which is read by genlop to generate the
output.

Also I don't think there is an option in portage to not log binary merges.

[1] https://bugs.gentoo.org/120899

--
Best
Daniel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 6 Mar 2022 09:50:00 +0100, Daniel Pielmeier wrote:

Dale schrieb am 06.03.22 um 06:53:

I have a chroot environment that I do updates in.  Once the updates
are done, I copy the binaries and distfiles over to my running system
and use the -k option to update everything in my real system.  It
comes in real handy when libreoffice, Firefox, qtwebengine and other
large time consuming packages are being updated.  The bad thing is, I
have the full length of build time in the chroot but the binary
install on my running system.  Is there a way to either stop it from logging binary updates or removing them after it is done?  I'd rather
it not keep those times in either place really.  I can't find a
emerge option.  It seems to record everything regardless.  My reason
for this, the binary install times throws off genlop -c and its
estimates.

There is a long-standing bug [1] regrading this issue but given genlop currently is not actively developed I don't think there will be a
solution soon. It should be possible to exclude binary merges as they
can be identified in emerge.log which is read by genlop to generate the output.

Also I don't think there is an option in portage to not log binary
merges.

It looks that way, man emerge says

/var/log/emerge.log
Contains a log of all emerge output. This file is always
appended to, so if you want to clean it, you need to do so
manually.

However, genlop can, AFAIR, be pointed to a different log file, so you
could maybe use grep or sed to remove the binary entries and output to a
log that is read by genlop.

However, I do wonder why the chroot and the host are both writing to the
same log file, surely the chroot builds are logged within the chroot.


--
Neil Bothwick

New sig wanted good price paid.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmIks2kACgkQ92eFu0QS MJhxDA//crngNFXrw+9xZd1qyb4p+1l5uNiHLv45njdqN/s8rHpuJddEAxZSCO+d rD6tJd5aoJBqczWACyRqNQrVbBvOQBOtvI2Wa4V7mrBTDHjpOSXRP0GzGjlPyYrA iUtudUVJn5L4rkGiRow25SCVGvYH8tLsQHel67k6Gb7p9jDsYXGjeVuJ+iCAe/Zm RVlCfXicjd8PQK56lhzvrAKEtlaE9J+LtA5ua5PXTbqrnJWPr7RpumtCJnDgQZfu g0/YygLA2s6bB4QEe0uQtZDXxVTXURbk63X6UlBgpQHzqdycTxnqn6/rMLYIga8Q QeGUuUNOwh0XRpquV5DJaGKPfedaFaY6r3v3SugVcA0Rxmpx80Vituw81iiU1CTi 1q1tGuG21CM7uFtQi8CSbhJz10in8XWMyYHJ48Bca+6kHbEUwb4FP1wdXAL30Qxm jadGLghOf/Tb5Oq8L2qy5PFCVhEuUZ7q3nxenBuddOIz8IhZAK76vQESUzJwDta4 J/zyMwe4788HvFvuohhhNlG4tNpJG6XNYhddLXF8g6NHku/OfTxyaw+6WZ3WQG/Y l9x5b9t2Hi+9//V4veZ5A0yhKjxxrICEHaXXQtU7QTasvlPxacKs+WRyiHPEsLvp maq7KBrUIUIo4uMlX7mT45bIZUwvUlrYBm/mR03rOwr9YCAB/JA=
=GaQD
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Neil Bothwick wrote:

On Sun, 6 Mar 2022 09:50:00 +0100, Daniel Pielmeier wrote:

Dale schrieb am 06.03.22 um 06:53:

I have a chroot environment that I do updates in.  Once the updates
are done, I copy the binaries and distfiles over to my running system
and use the -k option to update everything in my real system.  It
comes in real handy when libreoffice, Firefox, qtwebengine and other
large time consuming packages are being updated.  The bad thing is, I
have the full length of build time in the chroot but the binary
install on my running system.  Is there a way to either stop it from
logging binary updates or removing them after it is done?  I'd rather
it not keep those times in either place really.  I can't find a
emerge option.  It seems to record everything regardless.  My reason
for this, the binary install times throws off genlop -c and its
estimates.

There is a long-standing bug [1] regrading this issue but given genlop
currently is not actively developed I don't think there will be a
solution soon. It should be possible to exclude binary merges as they
can be identified in emerge.log which is read by genlop to generate the
output.

Also I don't think there is an option in portage to not log binary
merges.

It looks that way, man emerge says

/var/log/emerge.log
Contains a log of all emerge output. This file is always
appended to, so if you want to clean it, you need to do so
manually.

However, genlop can, AFAIR, be pointed to a different log file, so you
could maybe use grep or sed to remove the binary entries and output to a
log that is read by genlop.

However, I do wonder why the chroot and the host are both writing to the
same log file, surely the chroot builds are logged within the chroot.

Well, as it is, I copy the emerge.log file over so that I have the
actual build time when I copy over the binaries and distfiles.  Thing
is, when I emerge the binaries, it adds that to the file too.  So, half
of file is build and half binary.  Of course, the binaries is a lot
faster so genlop just has a bad day.  ;-)

Guess I have to tolerate it for now. 

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)