去不工作/去另一个地方去

Question

I'm trying to go get a project that was initially hosted on a defunct/unavailiable A.com server. The same project is now served under B.com but all imports inside the code are pointing to A.com (eg. import A.com/user/projet/lib).

When I try to go get B.com/user/projet it's cloning the git repo from B.com but then tries to download resources from A.com.

How can tell go get that the package A.com/user/projet is now served at B.com/user/projet (without rewriting imports inside the code) ?

Answer 1

There is another dirty trick no one mentions - manually git clone, git pull package in $GOPATH/src/A.com/package, before maintainer will rewrite imports himself. go build, go install work as expected. I do this time to time as quick hack.