-
Notifications
You must be signed in to change notification settings - Fork 11
Proposal: officially deprecate gobin as of Go 1.16 #103
Comments
The stress test CI job has been failing due to an error in bootstrap: https://github.com/mmcloughlin/addchain/runs/2129921772?check_suite_focus=true#step:5:24 The problem relates to `gobin` under Go 1.16 myitcv/gobin#103. This PR fixes the issue by using a `tools.mod` file to manage tools dependencies as suggested in: https://www.bwplotka.dev/2020/bingo/ https://github.com/prometheus-operator/prometheus-operator/blob/5a2412883718ffe889fe741d5e0e5e7ae6b5f183/scripts/go.mod
Thanks for raising this discussion. I have hit this issue in a couple of repositories so far: mmcloughlin/avo#166 However in both cases I've been able to easily deal with it by switching to the preferred So from my point of view I think deprecating |
I also agree that deprecating gobin is a good option right now. I seem to recall that Jay and others want to collect data and user reports on how they are affected by the limitations of |
I've also added a note to the description that a proposal to support |
Once we merge this PR we will archive the project. Fixes #103
Once we merge this PR we will archive the project. Fixes #103
Apologies for being slow at getting round to raising this issue. Thanks to @howardjohn for raising #102.
Go 1.16 supports
go install $pkg@$version
to install commands without affecting the main module. This is the default mode of operation forgobin
.But another change in Go 1.16:
means that changes are required in
gobin
for it (gobin
) to continue to function when usingcmd/go
1.16 (tests currently fail for example)It's not clear to me however that it is worth making these changes (although I would be very open to someone else making the required changes). Whilst these Go 1.16 changes do not entirely cover the
gobin
use cases,go install $pkg@$version
is generally sufficient.Also noting the recently accepted proposal to support
go run $pkg@$version
, which should hopefully land in Go 1.17.However, I'm raising this issue for discussion in case others disagree.
cc @rogpeppe @mvdan (and @mmcloughlin from a
#tools
message on Slack)The text was updated successfully, but these errors were encountered: