AFAICT, go build tags are a compile-time only construct, so there is
no way to query whether a certain package was built with a specific
tag. However, the 'netgo' tag triggers conditional compilation of the
cgo_stubs.go file, and that file name ends up in the executable. (we
could have looked for specific symbols in the 'net.a' library instead,
but that requires locating it first, which is more hassle than it is
worth)
issue #93
by using go's internal DNS resolver.
NB: this relies on go's std library having been compiled with the
netgo build tag, e.g.
sudo go install -tags netgo -a std
issue #93
...and docker-ns (though we still leave the script around since it's
handy for debugging), and arping (as I have yet to encounter a
situation where it was required)
Matthias Radestock