Closed markmandel closed 10 years ago
The reason of the -u
to be there is the following: imagine you at some point want to change the version for a package in your Godeps
and you put a newer tag or version hash that didn't exist by the time you installed it in the first place - which should be pretty common - what will happen is that gpm will fail because it won't be able to checkout said version, thus the need to force update of the repos.
I agree we should find a way to work around this in some way, but removing -u
I feel breaks a common use case, let's consider other options first and see what we can come up with.
Yeah, I had a feeling that may be the case (side note: should considering integrating that scenario into the tests, so that travis fails when that happens)
Of course that means that will also never work for the scenario provided, as it fails on those gae dependencies.
Maybe a flag in GPM to turn off the -u is the correct option (have it on by default) could be the easy way to go.
Agreed this is a bad idea. Closing.
This breaks GAE applications that use go, and libraries that use app engine dependencies that are stored in the appengine GOROOT.
You get errors like this:
Let me know if this will break other things, maybe there is an alternate workaround for this issue.