On Fri, 11 Jan 2013, Kevin Fenzi wrote:
On Fri, 11 Jan 2013 12:16:50 +0000
"Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:
On this theme, one other very useful thing we could improve in Koji
for developer debug of failed builds, would be to capture the
'config.log' file from any autoconf based builds.
Currently when I get stuck with configure problems I have to hack the
spec file todo "%configure || cat config.log". It'd be nicer to have
config.log as a standalone published file though, because sometimes
you have a successful build but later want to go back and see why
configure chose a particular thing and you're lacking config.log at
that point.
Perhaps this is something mock could be enhanced to do?
Then koji would (mostly) get it by default from mock...
Could probably be easiest done as a mock plugin. Have it look for a
config.log in the build dir and have it pull it out to the results dir.
Not sure what it would do in the even it found more than one, though.
-sv
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
