| 1 |
On Thu, Jun 11, 2015 at 08:58:37AM -0700, Andrew Udvare wrote: |
| 2 |
> |
| 3 |
> > On 2015-06-11, at 08:38, William Hubbs <williamh@g.o> wrote: |
| 4 |
> > |
| 5 |
> > this eclass is meant to provide a common src_compile function for |
| 6 |
> > packages written in the Go programming language. |
| 7 |
> > |
| 8 |
> > Let me know what you think. |
| 9 |
> > |
| 10 |
> |
| 11 |
> I am wondering about bug 503324 and the issue of needing to create a GOROOT with everything except the package to be compiled. Is your way solving this issue? |
| 12 |
|
| 13 |
I looked at an example in the tree (specifically go-fuse) and the |
| 14 |
src_compile I wrote is the same as the one there. |
| 15 |
|
| 16 |
In the testing I've done here, GOPATH must be set or "go get" doesn't |
| 17 |
work. The newest code for packages will always be stored in the first |
| 18 |
directory listed in GOPATH, not in GOROOT. |
| 19 |
|
| 20 |
Given how GOPATH works in relation to GOROOT, I don't know yet why the |
| 21 |
ebuilds in the tree are copying goroot; I'm not quite sure what they are |
| 22 |
working around yet. |
| 23 |
|
| 24 |
For more info, look at "go help gopath" and "go help packages". |
| 25 |
|
| 26 |
Let me know what you think after reading those. |
| 27 |
|
| 28 |
William |
Archives