-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: go get takes very long time on projects with a lot of history #18423
Comments
We once tried shadow clone, but it broke things and was
rolled back. See https://golang.org/cl/16360 for the CL,
and https://golang.org/cl/16832 for the rollback.
|
Make an optional feature enabled command line argument then maybe? Something like '--shallow' that would call git clone --depth 1? |
That project is just one of many with which I see that. Some other projects may take unbearably long. Right now I just resort to doing a "git clone --depth 1 https://www.github.com/user/project $(GOPATH)/src/github.com/user/project/" which is rather annoying if there are multiple dependencies to fetch |
Do you use Windows+antivirus perhaps? |
No. I am using Mac/Linux and I am located in PRC at the moment. From here Github is accessible but rather slow. And this isn't the only place this happens. Same is half of South East Asia and Oceania, except Japan and Korea perhaps. |
Related to #13078. I don't have a quick fix for you. I hope the long-term package management story will solve this, by not requiring full Git checkouts. For now I will leave the issue open for tracking purposes. |
In module mode,
As far as I can tell this seems to be resolved. |
What version of Go are you using (
go version
)?1.7.4 darwin
What did you do?
go get guthub.com/andlabs/ui
What did you expect to see?
Since we only need/expect latest version the shallow copy of repository is expected.
What did you see instead?
The full
git clone
which since there are binary files checked in and they were updated multiple times takes ~30 minutes to execute.The text was updated successfully, but these errors were encountered: