Re: Go & bundling

[Leo Famulari <leo@famulari.name>]

On Mon, Jul 25, 2016 at 11:06:14PM -0500, Alex Griffin wrote:
> Leo Famulari <leo@famulari.name> wrote:
> > If that manifest is a standard thing, we could make a go-importer that
> > used it to create new packages.
> 
> The manifest is not standardized, or rather, there are too many
> competing standards.

Indeed. I looked into some other Go programs, and I found a variety of
manifest formats.

> If we are going to unbundle packages, I think it would be best if our
> code ignored any manifest files entirely. Versioning is a mess in the Go
> ecosystem, and usually the version specified in them only reflects the
> most recent commit that the developers had on their machine when they
> ran the vendor command. Rarely is it an actual tagged, stable release.

Right, it seems that dependencies are referred to by Git commits and
URLs (is it ever not Git?). So, we could end up with *a lot* of
different versions of each library in the package tree.

> BTW, the following command will probably be useful. It lists the
> dependencies of the current package (whose source is in the current
> directory), minus the stdlib.
> 
>     go list -f '{{join .Deps "\n"}}' | xargs go list -f '{{if not
>     .Standard}}{{.ImportPath}}{{end}}'

Thank you! I will play with this.