From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] runc: new package
Date: Thu, 26 May 2016 22:01:08 +0200 [thread overview]
Message-ID: <20160526220108.337d1590@free-electrons.com> (raw)
In-Reply-To: <1464292309.2374.38.camel@infradead.org>
Hello,
On Thu, 26 May 2016 12:51:49 -0700, Geoff Levand wrote:
> Go expects the developer to have a 'workspace' with a
> prescribed directory layout. Many projects archive their
> sources with a truncated path, so when they are extracted
> to a directory (@D in buildroot's case) things need to be
> fix enough for the go compiler to work. This is a common
> situation, and these fixups are often seen in project
> build scripts.
>
> See https://golang.org/doc/code.html#Workspaces
I have no problem with Go requiring a "workspace" to have a certain
organization. But why does these workspaces all need to be in
$$GOPATH ? Why can't $(@D) for each package contain a workspace ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-26 20:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 23:31 [Buildroot] [PATCH v3 0/3] Add docker engine support Christian Stewart
2016-05-25 23:31 ` [Buildroot] [PATCH v3 1/3] runc: new package Christian Stewart
2016-05-26 19:12 ` Thomas Petazzoni
2016-05-26 19:51 ` Geoff Levand
2016-05-26 20:01 ` Thomas Petazzoni [this message]
2016-05-26 20:21 ` Christian Stewart
2016-05-27 5:23 ` Thomas Petazzoni
2016-05-25 23:31 ` [Buildroot] [PATCH v3 2/3] docker-containerd: " Christian Stewart
2016-05-26 19:29 ` Thomas Petazzoni
2016-05-26 23:10 ` Christian Stewart
2016-05-25 23:31 ` [Buildroot] [PATCH v3 3/3] docker-engine: " Christian Stewart
2016-05-26 19:34 ` Thomas Petazzoni
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=20160526220108.337d1590@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.