Comment 1:

https://groups.google.com/forum/#!topic/golang-dev/RgHGBXROeAw

Comment 2 by yiyu.jgl:

An alternative solution is to use a special package. For example, include in your
repository an import.go file with:
    package importPath
    
    import _ "rsc.io/pdf"
When go get finds an importPath package, it checks that it has a single import whose
path matches with the one defined by the directory name (or, alternatively, that the
imported url doesn't resolve to it, as initially proposed by rsc in golang-dev). The go
tool would otherwise ignore importPath packages, which would never be built.
I think this approach has several advantages:
- It doesn't require any change to the language or the compiler.
- It is unlikely that additional info will creep into the import.go file (as with a
.json file).
- Vendoring becomes a matter of only rewriting import paths (current tools already work
with no changes!).
- This same method could be extended to support more than one import path, although I'm
not sure we would want to do that.
One drawback that I see is that godoc would also need to be aware of importPath
packages, but it won't be more difficult than making it understand the modified package
clause.
By the way, the importPath name is of course arbitrary. I'm sure there will be some
better option. My point is that it is easy to avoid conflicts with existing package
names (something like Path or ROOT would also work, there are more radical solutions
such as "package ." or "package import" which I find less appealing because they would
require a language change).

Comment 3:

CL https://golang.org/cl/124940043 mentions this issue.

Comment 4:

This issue was closed by revision 0c61467.

Status changed to Fixed.

Comment 5:

CL https://golang.org/cl/127210043 mentions this issue.

Comment 6:

This issue was closed by revision 3763a39.