You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This affects golang.org/dl/internal/genv package too.
The text was updated successfully, but these errors were encountered:
dmitshur
changed the title
dl/internal/version: go-import meta tag isn't served
godoc/dl: go-import meta tag isn't served for golang.org/dl/internal/{version,genv}
Aug 13, 2018
True, but kinda low priority, no? This only affects people trying to go get those internal packages directly, rather than go-getting the actual go1.N.M commands?
Yes, this is a very minor issue. Anyone just doing go get golang.org/dl/gox.y.z isn't affected. I just filed it because I ran into it (couldn't read the package's source code/docs).
dmitshur
changed the title
godoc/dl: go-import meta tag isn't served for golang.org/dl/internal/{version,genv}
x/website/internal/dl: go-import meta tag isn't served for golang.org/dl/internal/{version,genv}
Feb 27, 2019
Yeah, as far as I can tell, because of how package → module resolution works (documented at https://go.dev/ref/mod#resolve-pkg-mod), in module mode it appears to be sufficient as long as ?go-get=1 works on the module root. At least I'm not aware of any concrete ways that this issue is a problem in module mode.
I can close this issue for now, and consider reopening if we find a good reason to.
https://golang.org/dl/internal/version?go-get=1 is 404.
It should be serving something similar to https://golang.org/x/tools/go/vcs?go-get=1, etc.
This causes https://godoc.org/golang.org/dl/internal/version to show not found, etc.
This affects
golang.org/dl/internal/genv
package too.The text was updated successfully, but these errors were encountered: