Closed michaeltrobinson closed 6 years ago
This needs to be fixed in the same way it was fixed for git. Resolving the symlink isn't acceptable. If mercurial is resolving the symlink then we need to change the behavior of mercurial to provide a path w/o resolving the symlinks for us. See also: https://github.com/tools/godep/commit/446e2f61cbc0bfa616de9b4b0cf6271945704a77
I'm open to suggestions, but I haven't been able to figure out any way to get the un-resolved vcs root out of hg
(but I am by no means a mercurial expert).
ditto and mercurial is horribly untested inside of godep. ;-) I'll see if I can take a look later.
Thanks, but I am closing this PR because the repo is going to be archived.
This fixes an issue that occurs when your GOPATH contains a symlink and the dependency uses Mercurial.
Here is the minimal test program to show the problem:
As you can see, it skipped the
goautoneg
files./Users/michaelrobinson/.gvm/pkgsets/go1.6.2/global/src
is a symlink.With the proposed changes:
My GOPATH/GOROOT
GOPATH=/Users/michaelrobinson/.gvm/pkgsets/go1.6.2/global:/Users/michaelrobinson/code/go
GOROOT=/Users/michaelrobinson/.gvm/gos/go1.6.2
/Users/michaelrobinson/.gvm/pkgsets/go1.6.2/global/src
points to/Users/michaelrobinson/code/go-thirdparty/src
The dependency in question (
bitbucket.org/ww/goautoneg
) uses Mercurial.