[Buildroot] [RFC PATCH v1 1/6] package/go: implement go modules integration

Christian Stewart christian at paral.in
Mon Apr 8 02:04:00 UTC 2019

Hi Thomas,

Thomas Petazzoni <thomas.petazzoni at bootlin.com> writes:
> While browsing through the list of pending patches, I found the
> following patch series related to Go and package management:
>   http://patchwork.ozlabs.org/project/buildroot/list/?series=68102
> The first patch in the series,
> http://patchwork.ozlabs.org/patch/976322/, introduces:
> +	  Glide is a tool for managing the _vendor_ directory within a Go
> +	  package. This feature, first introduced in Go 1.5, allows each
> +	  package to have a _vendor_ directory containing dependent
> +	  packages for the project. These vendor packages can be
> +	  installed by a tool (e.g. glide), similar to go get or they
> +	  can be vendored and distributed with the package.
> and it does a fair amount of changes in pkg-golang.mk.
> How does this fit (or not) with the changes you're proposing ?

Glide and other tools were built before Go modules were built. I do not
recommend integrating them into Buildroot. They are on the way out.

Please see the Go module wiki:


  go mod init automatically translates the required information from
  dep, glide, govendor, godep and 5 other pre-existing dependency
  managers into a go.mod file that produces the equivalent build.

The Go developers left it up to the community to develop a source
package manager, which is why Glide, Dep (gopkg.toml), vendor.conf, and
other formats exist. These formats are intended to be completely
replaced by go.mod.

My suggestion is to instead solve the Go module stuff, and then bring in
Glide-based packages with the glide.lock file converted into the Go
module format via the above automatic process.

Best regards,

More information about the buildroot mailing list