search

adrianco / spigo

Simulate Protocol Interactions in Go
Apache License 2.0
1.12k stars 111 forks source link

Building after a fork #70

Closed hvandenb closed 8 years ago

hvandenb commented 8 years ago

What's the best way of building the project with go when you have forked the project? It seems to have issues with finding the packages that are within the local directory. The GO* variables are all setup, but using go build in the root keep failing.

My go build keeps failing with the packages local. I can use go get to get the packages but that just places them in those directories. I'd like to make improvements to the packages.

Here's an example

../../adrianco/spigo/actors/edda/edda.go:5:2: cannot find package "github.com/adrianco/spigo/tooling/archaius" in any of:
    /Users/me/tools/go/src/github.com/adrianco/spigo/tooling/archaius (from $GOROOT)
    /Users/me/projects/gocode/src/github.com/adrianco/spigo/tooling/archaius (from $GOPATH)

Settings:

GOROOT=/Users/me/tools/go
GOPATH=/Users/me/projects/gocode
adrianco commented 8 years ago

I'm not sure how to handle this. When I was working with a modified fork of someone elses code I manually changed the includes to reference it.

hvandenb commented 8 years ago

I'll give that a shot. It seems to be an as designed limitation in go.

hubayirp commented 8 years ago

This might help - http://code.openark.org/blog/development/forking-golang-repositories-on-github-and-managing-the-import-path

On Wed, Jun 1, 2016 at 8:56 PM, Henri van den Bulk <notifications@github.com

wrote:

I'll give that a shot. It seems to be an as designed limitation in go.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/adrianco/spigo/issues/70#issuecomment-223189521, or mute the thread https://github.com/notifications/unsubscribe/ACWGWFhT6UDw8hiRxrIypZyqOJfNdPEEks5qHlSKgaJpZM4IjcZd .

hvandenb commented 8 years ago

Thanks @hubayirp that's a great help. Closing issue.