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

:-)  :-) 



Reply via email to