New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/32016#issuecomment-882118894

Comment:
 > I don't really follow what you mean with that? As in, I understand the go-bootstrap package, but I don't follow how this relates to this change/commit? We don't really build anything with Go directly, it just uses the make.bash script (which assumes Go 1.4).

This matters because the Go binaries would have been built with the old toolchain, so its runtime also needs to support stripped binaries. But I think we do a double bootstrap, so it might not matter after all. Would have to check.

> As for the pre-built stdlib, personally I don't really see a reason to ship it; especially for containers etc. it's comparatively large, and unlike Python's .pyc files they can just be generated as-needed, which also keeps all the Go cache in one place which is kinda nice IMO.

It's bigger for a container, but it's a "time saver", possibly... I'd like to have thoughts from other before merging that part.

> We'd have to add back nostrip back with the manual strip call if we do decide to add it btw, as the strip hook will try and fail to strip those .a files.

Ugh :/ That's a reasonable reason for it, unfortunately.