Skip to content
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

Proposal: add a flag to go get to respect replace directives #47380

Closed
firelizzard18 opened this issue Jul 25, 2021 · 1 comment
Closed

Proposal: add a flag to go get to respect replace directives #47380

firelizzard18 opened this issue Jul 25, 2021 · 1 comment

Comments

@firelizzard18
Copy link
Contributor

What version of Go are you using (go version)?

$ go version
go version go1.16.5 linux/amd64

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GOARCH="amd64"
GOOS="linux"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVERSION="go1.16.5"
GCCGO="gccgo"

Proposal

go get <url> does not respect replace directives in the top-level go.mod of <url>. #30354 has been referenced by nearly 40 issues in other repositories, many/most of which boil down to "this doesn't build because replace directives aren't respected by go get <url>. Clearly many people expect replace directives in a top level module to be respected when that top-level module is fetched with go get. So I propose to add a flag to go get to enable this behavior.

@gopherbot gopherbot added this to the Proposal milestone Jul 25, 2021
@seankhliao
Copy link
Member

Duplicate of #44840

@seankhliao seankhliao marked this as a duplicate of #44840 Jul 25, 2021
@golang golang locked and limited conversation to collaborators Jul 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants