Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v1 1/6] package/go: implement go modules integration
Date: Sun, 7 Apr 2019 22:17:26 +0200	[thread overview]
Message-ID: <20190407221726.130ca0fe@windsurf> (raw)
In-Reply-To: <20190317012142.10545-1-christian@paral.in>

Hello Christian,

On Sat, 16 Mar 2019 18:21:37 -0700
Christian Stewart <christian@paral.in> wrote:

> This commit moves from the GOPATH mechanism to the new GO111MODULE approach for
> Go based packages. Old Go packages (with the exception of docker-cli) will
> compile without changes (for example, mender, flanneld).

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 ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2019-04-07 20:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17  1:21 [Buildroot] [RFC PATCH v1 1/6] package/go: implement go modules integration Christian Stewart
2019-03-17  1:21 ` [Buildroot] [RFC PATCH v1 2/6] package/runc: upgrade to go modules Christian Stewart
2019-03-17  1:21 ` [Buildroot] [RFC PATCH v1 3/6] package/docker-containerd: " Christian Stewart
2019-04-05  8:36   ` Arnout Vandecappelle
2019-04-05 10:58     ` Christian Stewart
2019-03-17  1:21 ` [Buildroot] [RFC PATCH v1 4/6] docker-cli: " Christian Stewart
2019-03-17  1:21 ` [Buildroot] [RFC PATCH v1 5/6] docker-proxy: " Christian Stewart
2019-03-17  1:21 ` [Buildroot] [RFC PATCH v1 6/6] package/docker-engine: " Christian Stewart
2019-03-27 16:50 ` [Buildroot] [RFC PATCH v1 1/6] package/go: implement go modules integration Thomas Petazzoni
2019-03-27 18:36   ` Christian Stewart
2019-04-05  8:32     ` Arnout Vandecappelle
2019-04-05 10:47       ` Christian Stewart
2019-04-05 14:07         ` Arnout Vandecappelle
2019-04-05 17:49           ` Christian Stewart
2019-04-05 21:59             ` Arnout Vandecappelle
2019-04-06  3:13               ` Christian Stewart
2019-04-07 20:17 ` Thomas Petazzoni [this message]
2019-04-08  2:04   ` Christian Stewart
2019-04-08  7:02     ` Thomas Petazzoni
2019-04-08  7:06       ` Christian Stewart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190407221726.130ca0fe@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox