mock ?'s

[Jeff Pitman]

On Thursday 06 October 2005 20:49, Rex Dieter wrote:
> Any
> pointers as to where to look for mock's intermediate build.log?

There isn't one.  Mock uses the commands lib which effectively does 
this: 
          pipe = os.popen('{ ' + cmd + '; } 2>&1', 'r')
          text = pipe.read()
          sts = pipe.close()

Then the text is written to the build.log after the command is complete 
using the build_log() function in mock. It does flush here, but it's 
only good for maybe the last block that's in the string buffer in 
memory.  Which can be good for failures that short circuit the close() 
in the cleanup phase. But, it means nothing as far as trying to get a 
realtime look at commands executing in the chroot.

To get realtime output of the command into the build.log would require a 
re-tool of the do() function.  This would also be good in the case 
where a patch didn't apply and it sits there asking which file it 
should apply it to.  In the past, I've typically just used "ps" to see 
what it's stuck on.

Being able to "tail -f" on the build.log outside of mock would be cool.

-- 
-jeff