Vgo implements a package manager which is suppose to download dependencies from some remote host. It determines where to fetch the code by looking at the import path of the dependency. Hence All dependencies which are managed with the new vgo mechanism musst follow this import path convention. Other dependencies are either the std lib, I guess this is a special case, or are packages which are below your project go.mod. As I understand it vgo does not respect the GOPATH any more, so it might not find packages which are just next to your package in the GOPATH.
As for your package "myapp" it should be sufficient to give the module a appropriate name in the go.mod file: module "my.domain/myapp" However this would make it not usable as a dependency in other packages with vgo. 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.
