[arch-dev-public] Go 1.17 released - to rebuild or not to rebuild

[Morten Linderud]

Yo,

I packaged up the new Go release yesterday and moved it over to stable earlier
today. 

Usually new Go minor releases frequently include new compiler improvements and
some assorted runtime changes. Previous releases I have done complete rebuilds
of Go packages in our repositories but the reception for these rebuilds have
been a bit mixed.

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.

But on the other hand I'm not super eager to be alone rebuilding all of this
either. So what are peoples thoughts on the subject?


Go 1.1 release notes: https://golang.org/doc/go1.17 
Previous rebuild: https://archlinux.org/todo/go-116-rebuild/

-- 
Morten Linderud
PGP: 9C02FF419FECBE16
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20210817/eea2f4fb/attachment.sig>