Problem: hibernate-ram, ^Z, and other things that temporarily pauses emerge breaks the logged merge time. $ genlop -t firefox * www-client/firefox Sun Oct 21 03:45:15 2012 >>> www-client/firefox-10.0.7 merge time: 21 minutes and 5 seconds. Wed Oct 24 12:24:57 2012 >>> www-client/firefox-10.0.9 merge time: 22 minutes and 6 seconds. Wed Oct 24 13:32:04 2012 >>> www-client/firefox-10.0.9 merge time: 20 minutes and 3 seconds. Sat Nov 3 22:45:56 2012 >>> www-client/firefox-10.0.10 merge time: 7 hours, 8 minutes and 18 seconds. Solution: use a timer that is paused along with emerge.
We'd have to extend the format of /var/log/emerge.log to indicate the relationship between clock time and actual run time, and then tools like genlop would have to be able to interpret the extended log format. I really don't think that it's worth the effort, because people typically don't need to sigstop/sigcontinue builds like this.
(In reply to comment #1) > people typically don't need to sigstop/sigcontinue builds like this. [citation needed]? Because all of the people I know and talk to at school that run Gentoo Linux (granted, there's only four of us, but still) actually do this. being laptop users.
Okay, maybe it is a common practice for some people. I did it a couple of times in the past, but lately I just build an image on my desktop system and sync it to my laptop(s). For the log extension, I guess we could simply handle SIGCONT and add a line to the log to indicate that emerge has resumed. Then tools like genlop could subtract the time between that log entry and the previous one.
(In reply to comment #3) > For the log extension, I guess we could simply handle SIGCONT and add a line > to the log to indicate that emerge has resumed. Then tools like genlop could > subtract the time between that log entry and the previous one. I suppose that would work just as well.
