A couple of initial questions: - The "pretend you're importing github.com/foo/bar but actually pull it from localgit.host/foo/bar" functionality of dep was going to really simplify things for us. I can't quite tell whether vgo includes that functionality or not. We would want to do it at the monorepo level: ie. *everything* should use our forked version of the `glog` and `protobuf` packages. - For our (go monorepo) usecase: do you envision a single go.mod file being placed at the root, or would we sprinkle them as needed for each sub-project in the monorepo? Does vgo search upward for go.mod files? - More details on the zipfile module representation will be welcome. - Getting rid of GOPATH is nice. Where will `vgo install` drop binaries? Thanks for your work on this. It looks very “Go-ish”. Interested to learn more.
Zellyn On Tuesday, February 20, 2018 at 12:20:54 PM UTC-5, Russ Cox wrote: > > Hi everyone, > > I have a new blog post you might be interested in. > https://research.swtch.com/vgo. > > I'll try to watch this thread to answer any questions. > > Best, > Russ > > > > -- 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.
