I'm not saying it shouldn't work as you try to do it. I thing vgo is a very early prototype many corner cases seem to be unsolved. Your problem arises because the old mechanism (GOPATH) is not there anymore. I actually think that your replace workaround should work, so maybe you should file an issue. If this is good practice is a different topic.
I would rather restructure my source a bit to make it work (e.g. make mylib a child of myapp) than requiring some proxy infrastructure. Am Freitag, 23. Februar 2018 11:15:54 UTC+1 schrieb wilk: > > Hi, > > I work with GOPATH per project. > > Then I use to give them a one word path directly under src: > > $GOPATH/src/myapp > > But I found that it doesn't work with vgo. It looks at > /usr/local/go/src/ instead of my GOPATH. > The same when i use replace with a clone of a libs. > > If there is a dot in the package name it works > > $GOPATH/src/my.domain/myapp/ > > Should i submit an issue or shoud i forget quickly this bad practice ? > > -- > William > > -- 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.
