[Buildroot] [PATCH v3 1/3] runc: new package
Thomas Petazzoni
thomas.petazzoni at free-electrons.com
Thu May 26 20:01:08 UTC 2016
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
More information about the buildroot
mailing list