How does the source manager handle the case of two URLs to the same location. For example,

• https://github.com/foo/bar
• git@github.com:foo/bar

This case can arise in a global cache where two different projects specify the same location two different ways.

In some systems the (e.g., private git installs) there may be a difference in available branches (e.g., private branches) and the access that entails. Don't need that to leak.

How does the source manager handle this so it can be used in the GOPATH and scanning?

Glide handles this by creating a key for the cache that's based on the URI. So, the two examples above would be two different cache entries.