You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For package vendoring dependencies, (like coreos/etcd) nested dependencies will never get resolved locally, as the import path is app, instead of the fully qualified one.
A proper solution is to allow package who vendor dependencies to specify their original import path with a .godir text file or through Godeps, and default on app only if the fully qualified import path cannot be infered.
The text was updated successfully, but these errors were encountered:
proppy
added a commit
to proppy/golang-docker
that referenced
this issue
Jun 12, 2014
For package vendoring dependencies, (like coreos/etcd) nested dependencies will never get resolved locally, as the import path is
app
, instead of the fully qualified one.A proper solution is to allow package who vendor dependencies to specify their original import path with a
.godir
text file or through Godeps, and default onapp
only if the fully qualified import path cannot be infered.The text was updated successfully, but these errors were encountered: