If GIMME_DEBUG >= 2 then make.bash -v

[philpennock]

We already have logic to handle GIMME_DEBUG looking like a number and capturing more output here; just use one number higher to ask make.bash to be verbose.

Slightly repetitive, but cleaner and easier to understand than conditional arrays or stuff which would affect shellcheck if we relied upon empty unquoted args being dropped.

With this and without the #159 unset of GO111MODULE, invoking as GIMME_DEBUG=3 GO111MODULE=on gimme master reveals all the use of internal package complaints which show that building Go itself is incompatible with having GO111MODULE set in environ.

[AlekSi]

We already have logic to handle GIMME_DEBUG looking like a number and capturing more output here

Personally, I would like to see that logic simplified: if GIMME_DEBUG is set and not zero, enable debugging output. No need for different levels – it is already debug level.

[philpennock]

There's a difference between "debugging gimme" and "debugging everything gimme runs". Stacked debugging levels can be helpful.

But really, I can't see a reason to want the output of make.bash captured but to not want it to be verbose, so I'll simplify back to "no more complex than before" and make it be "capture make.bash -v" vs "don't capture". Good call.

[joepvd]

Thanks!