packaging: -x and -v make it difficult to diagnose build failures

[W. Michael Petullo]

I maintain a number of Go packages for Fedora, including Hugo. I find that
the default use of -x and -v when running "go build" makes it difficult to
diagnose compile problems. A compile error does not necessarily terminate
the Go build process, and with -x and -v the error message is quickly
lost in the volume of output from go build.

I have figured out how to run "go build" in mock without the -x and -v
flags, but I sometimes have to diagnose the build log from the Fedora
build server, and this is very difficult due to the volume of output.

For an example of this, see:

	https://kojipkgs.fedoraproject.org//work/tasks/3319/88593319/build.log

I would rather not redefine the default "go build" flags for my
packages. Has there been any thought put into dropping -x and -v?
Does anyone else have trouble with this? Does anyone benefit from the
use of -x and -v? Am I missing an obvious trick?

-- 
Mike

:wq