How exacly would this syntax work with multiple packages, while still keeping backwards compatibility?

Also note that such a large change should come in the form of a proposal with much more detail.

Well, as in case of other languages - if you are specifying exact thing to get - it's your problem that it does not work. I personally know many people who are using additional tools/dirty hacks to get this functionality.

Adding the naive matching is better that nothing in such scenario.

Sorry, this is my first work with golang codebase, I'll look up how to create proposals in more formal way.

If you want to specific version, you should use https://github.com/golang/dep instead

Adding the naive matching is better that nothing in such scenario.

I don't see how. Doing go get foo.com/foo bar.com/bar means one thing currently and is completely unambiguous. How do you propose to keep backwards compatibility with that while adding the versions like you showed?

Perhaps I'm missing something very obvious, but it seems to me like the syntax is still ambiguous. In the original post you mentioned tags as well as hashes. How are you going to discern if a string is a tag or an import path? Note that both can be foo.com/bar.

or you can use git submodules.

The lack of this ability make impossible to install older version without becoming crazy.

My use case: i need to install https://github.com/google/cloud-print-connector
But go 1.9 give segmentation fault, so i installed go 1.8, but the projet is using 1.9 in the last version.
Result:
i cant install what i need, and I blame go. Twice.

BTW totally ok to support commit hash only if that is the issue. Somethng is way better than nothing

@MauroMombelli This issue is closed, for good reasons. There are some alternatives suggested above. Another is to run go get and then cd DIR; git checkout REV.

@MauroMombelli if you don't feel like using dep, I wrote a little tool for that https://github.com/OneOfOne/git-go-vendor, you should be vendoring your deps one way or the other anyway.

@ianlancetaylor is not checking out the correct version, is to make it complile with all dependency and such. I bring as example the https://github.com/google/cloud-print-connector, a official google product that break and i wanted to have.

@OneOfOne i would like to use it, but i tried some combinantion of parameter before giving up in frustration. I understand the "compile by yourself", but the "handle the dependency fun".. no thank you. I tryed to use another tool that supposely would give you a specific tag, but unfortunately it seems to use a different versioning schema that the project liked, thus making the build unsuccessfully.

@MauroMombelli This issue is closed and will not be reopened. If you want to discuss this further, please use a forum; see https://golang.org/wiki/Questions. Thanks.

glide seems to be path forward
after installing glide

• just run glide init
  just edit glide.yaml
  
  then glide update

Again, this issue is closed - please use one of the forums mentioned by @ianlancetaylor above to continue the discussion, or open a new issue if you have a specific proposal or suggestion in mind.