On 2021-08-17 21:36, Morten Linderud via arch-dev-public wrote:
People do not really see the need to rebuild $goWorld when packages a compiled and nothing inherently breaks unless there is a rebuild. We don't do this for GCC, Rust and so on. However I do think it's nice to group up these ecosystem changes in one swoop as it spares me from having to repeat myself for the next few months as people occasionally update their Go packages.
What are the relevant "ecosystem changes" in this case? In brief. Have the packaging guidelines been updated for 1.17 considerations?
Isn't there a CVE going around in a few projects that re-compiling with 1.17 will automatically catch and fix?