Makefile won't work with a symlinked project about open-service-broker-sdk HOT 7 CLOSED

working on this now

from open-service-broker-sdk.

The specific scenario under which I hit this issue does not yet work.

1. clone project to some directory
2. create a symlink to the project, locate the symlink in your GOPATH
3. attempt to build
4. fails

If I comment out the export GOPATH line in the Makefile everything works as I'd expect. I'm not sure if there are any other side effects of doing this though.

from open-service-broker-sdk.

1. checkout code directly into GOPATH, WORKS
2. checkout code directly into GOPATH, create symlink FROM another dir, WORKS
3. checkout code outside GOPATH, create symlink IN GOPATH, FAILS

from open-service-broker-sdk.

In general symlinks + golang == failure. There are long standing incompatibilities with golang and symlinks which are constantly closed by the golang core team with an explanation that golang does not support symlinks. Whenever anything comes along that works the golang core team's answer is "great that works, but it might not tomorrow, you must follow the golang way"

kubernetes and openshift try to make symlink hacks work when we know they can, but in general we will not invest time into making it work. After enough hits on the head it becomes apparent that if one can not change the golang core team the only option is to conform.

from open-service-broker-sdk.

@eparis that's understandable. But if I comment out the export GOPATH defined in the Makefile all three of my scenarios work fine. If it's not something we plan to fix, then I can close and just live with it.

from open-service-broker-sdk.

Fixed by PR #12

from open-service-broker-sdk.

closing since this was fixed, but we still have a bad "getting started" experience since we now rely on the user having a valid GOPATH defined, as well as a proper directory structure.

from open-service-broker-sdk.