Feature: rebuild with newer toolchain if available, even if version same

[scop]

Is your feature request related to a problem?

Even if an executable is up to date with the latest upstream, it may have been built with an older version of the Go toolchain than what is available on the system. Newer toolchains may fix bugs, improve performance etc in executables even if the upstream version has not changed.

Describe the solution you'd like

gup to take build and available toolchain versions into effect on check and update.

So if tool X is installed but built let's say with Go 1.22.2 and the system has Go 1.22.4 available, rebuild X with 1.22.4 as an update even if the upstream version does not change. And similarly for check.

Describe alternatives you've considered

Manually removing and reinstalling all executables when upgrading Go.

Additional context

https://pkg.go.dev/runtime/debug#BuildInfo GoVersion

[nao1215]

@scop

Thank you for your suggestion. I agree with your one.

However, the current specification of gup might already behave as you propose. gup always executes go install without checking the necessity for an update. I believe that executing go install will always update the binaries under $GOPATH/bin.

However, it might be necessary to output the go version (toolchain verison) used during the build process.

[scop]

Ah, that's right, it does indeed always update. But it also says "Already up-to-date" which is misleading, would seem that just addressing that and taking it also into consideration what to suggest updating in the gup check would be a good fix.

[scop]

WIP PR in #156. Contains some test failures still, but basics are there.