I'm frequently finding myself in a use-case where I'm working on multiple repositories simultaneously and the current Go vendor model just doesn't work. It would be awesome if glide supported a non-vendor mode where it updates the gopath instead of the vendor directory. I know this may be outside of glide's mission and it would be better if the Go vendor stuff worked for this use-case, but I thought I'd raise the issue here anyway.

Example use-case: I'm working on a library in one repo checkout out into my gopath and an app that uses the library in another repo checked out in my gopath. As I'm adding functions to the app I'm adding stuff to the library. Both have a number of shared dependencies. I don't know how to make this use-case work with vendor dirs 'cause that inevitably ends up with two copies of the same dependency, only in the app's vendor dir and one in the library's vendor dir or in the gopath if the library doesn't have a vendor dir.

The way I make things work is to cleanly manage my gopath manually (e.g. create a gopath for this overall project) and not use vendoring at all, which means that I recreate the dependencies listed in glide.yaml manually using go get. It would be awesome if I could tell glide install to put stuff into the gopath instead of the vendor subdir.