News for hackers. Stuff that matters.
Re:Three Minor Features in Go 1.18 by neild on Wednesday December 22, 2021 @11:15PM (#29658597)
Go builds are, in general, reproducible by default. Build stamps do not change this.
Re:Three Minor Features in Go 1.18 by cpuguy83 on Thursday December 23, 2021 @12:39AM (#29659009)
"reproducible by default" if the system is setup a certain way.

Build time injected into builds would absolutely break any reproducibility.

Re:Three Minor Features in Go 1.18 by thiht on Thursday December 23, 2021 @03:03AM (#29659705)
> "reproducible by default" if the system is setup a certain way

What do you mean? Under what circumstances is a Go build not reproducible? From what I’ve observed, if you build your binary with a set of input, the same binary is produced. Is it sometimes not true?

Re:Three Minor Features in Go 1.18 by cpuguy83 on Thursday December 23, 2021 @03:35AM (#29659875)
By default you need the same GOPATH and GOROOT.

Compiler version must be identical (not a huge stretch).

cgo reproducibility is not a guarantee.

Re:Three Minor Features in Go 1.18 by neild on Thursday December 23, 2021 @02:07AM (#29659432)
It would, which is why the Go compiler and linker do not put the build time in binaries.
Re:Three Minor Features in Go 1.18 by cpuguy83 on Thursday December 23, 2021 @03:30AM (#29659853)
But you literally said "build stamps do not change this", and it absolutely does. Of course as I mentioned it does not look like go is adding a build time to the binary.