On Sat, Sep 1, 2018, 11:43 AM Vasily Korytov <vkory...@4tifier.com> wrote:
> Hi, > > I've experimented with GO111MODULE preview in Go 1.11 release, two things > to note so far: > 1. go mod vendor pulled in vendor folder the .travis.yml file which > apparently I don't want there (govendor filters it by default) > > 2. I've decided to clean up my GOPATH and start from scratch. I moved > GOPATH and ran: go get something, but wasn't able to do it: > it complained with 'cannot find main module' and did nothing (despite the > target package had go.mod). Same procedure without GO111MODULE=on works > like a charm. > This point has been discussed before. The conclusion is that if you set GO111MODULE=on and run "go get", then it is expected that you are within a module location. Otherwise the Go tool has no idea where to cache the package you are getting. I may be summarising that incorrectly though, because it only makes partial sense to me. I get that it wouldn't know what you want to do with a library that is meant to be a dependency of a current module project. But I don't get why it shouldn't work for getting a main program. i.e. would expect it to work for getting something like goimports, where is it meant to just get and install a binary to $GOBIN > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
