I had an idea to add different exit codes to the go tool that would allow
programs that use it figure out what exactly went wrong. Right now I
believe exit code is always 1 if something went wrong.
But I want to know others' opinions on this, perhaps there's some reason
not to do so.
For example go build status codes would be something like:
0 - success
1 - package not found in GOPATH
2 - compilation failed
3 - permission denied opening source files/writing output file
There would be one single list for all tools, grouped up by type (e.g. 1-10
build-related errors, 10-20 go get related, etc.).
Original problem: I'm writing some very basic CI server, for no good
reason, and it's not very straightforward to figure out exact cause why
e.g. go get -u failed based on output and exit code.
If there are no reasons against this and if nobody had this planned
already, I'd like to give it a try and make a patch.
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.