Russ Cox

I filed https://github.com/golang/go/issues/57007 for building cmd/go without libc.so.6, which I think would make NixOS happy. I agree that it should be possible to build a toolchain with GOTOOLCHAIN=local as the...

> We should describe what happens if we drop an existing port (per https://go.dev/wiki/PortingPolicy). Presumably the go command 1.N will see "go 1.N+1", try to download the binaries for 1.N+1,...

> I guess I'm confused; my impression was that the hardest problem in upgrading was not obtaining a new version of Go, but making sure that the Go code works...

@mark-pictor-csec I think you just described the actual proposal. minimum_go is spelled 'go'. It sets the minimum Go toolchain version that must be used to compile the module, whether used...

**Re: potential confusion** A few people, including @ianlancetaylor, mentioned potential confusion. That potential definitely exists (indeed, many people on this issue are confused about the details, which suggests I did...

**Re: losing control over which Go toolchain is used** @zikaeroh raised a concern about whether Linux distributions would “lose control of the toolchain in use”, and @dominikh wrote that he...

This proposal has been added to the [active column](https://go.dev/s/proposal-status#active) of the proposals project and will now be reviewed at the weekly proposal review meetings. — rsc for the proposal review...

I agree that Origin and Reuse should provide enough information.

Does anyone object to doing this? (It's hard to imagine why anyone would object given that there is no Go code in these "modules".)

Having to create a .go file seems like a useful signal in this case.