gore can't import vendored packages

[robbles]

I'm trying to import a package inside a vendor subdirectory in my project. I get the following when importing directly:

gore> :import github.com/aws/aws-sdk-go
error: import: can't find import: vendor/github.com/aws/aws-sdk-go

I tried working around it by treating my vendor directory as a temporary GOPATH, and it worked:

ln -s $PWD/vendor /tmp/go/src
GOPATH=/tmp/go go install github.com/aws/aws-sdk-go
GOPATH=/tmp/go gore
gore> :import github.com/aws/aws-sdk-go
(no error)

This isn't really a workable solution though. Is there a way for gore to find these packages? I know they have to be go install'ed first - maybe that's part of the issue?

[syohex]

I suppose you need to specify absolute path of vendored package like github.com/your_name/your_product/vendor/github.com/aws/aws-sdk-go. go/importer package API which gore uses does not permit to import from vendored packages now.

[robbles]

@syohex It doesn't appear to work that way either. I've tried prefixing the vendored package as if it were under a package named vendor, and still get the same :import: can't find import error.

[syohex]

I cannot reproduce. Please try after installing package.

[james-lawrence]

it imports it just fine, but its not actually usable.

gore> :import example/vendor/github.com/nlopes/slack
gore> c := slack.New("junk")
package main
	imports example/vendor/github.com/nlopes/slack: use of vendored package not allowed
error: exit status 1
exit status 1

[jasiek]

Is this high on the list?

[jamescarr]

Yeah this is a bit of a nuisance.

[preeya-stripe]

+1

[motemen]

gore uses go run to evaluate user inputs, creating temporary .go file. The problem is that, in order to handle vendored packages correctly, you have to put the temporary .go file at current directory, which could make cwd dirty.

Anyway we could attack this, with carefully crafted temporary filenames. I'm going to work on this when I have time.

[motemen]

Also related to #69

[machinshin]

any updates on this?

[y00rb]

@syohex it looks only work under GOPATH, since go publish module feature, some project might not always under GOPATH. so that why someone meet issue can not load package in console. I'm a part of them.