Help Wanted: Guidance on Go Package Metadata

[kemitchell]

go list -f '{{ join .Deps "\n" }}' lists dependencies of the package in the current working directory. Is that the best way to inventory dependencies?

[kemitchell]

@coffeeboo, you inspired me to go ahead and take a crack at improving Go support. The master branch now recurses Go dependencies, even if they don't appear in the current working directory.

It can be a little slow, since I'm calling go list -f "..." $import for each dependency. I've done a bit of work to speed things up by skipping standard-library packages, but I'm sure there's more I could do.

[kemitchell]

I've just tagged this work as v4.3.0. Travis CI should have binaries ready for us in a few minutes.

[kemitchell]

To summary the approach as of 05d2cb1:

1. Run `go list -f '{{ join .Deps "\n" }}' and split its output for a list of all dependencies.
2. Iterate the list of dependencies:
   1. Skip those with known standard-library import names.
   2. Run go list -f $template $importfor the rest, parsing out name, path, import path, and whether it's a standard-library package.
   3. Try to read licensezero.json in the path for all non-standard-library packages.