The ebuild for this new version fetches now 11 files with each about 50 MB in size. Required is normaly only one of them, thus about 500 MB will be unnecessarily downloaded. This probem is caused by this change: diff -ruN go-1.12.ebuild go-1.12.1.ebuild --- go-1.12.ebuild 2019-03-17 03:46:08.000000000 +0100 +++ go-1.12.1.ebuild 2019-03-17 03:46:08.000000000 +0100 @@ -13,19 +13,17 @@ BOOTSTRAP_DIST="https://dev.gentoo.org/~williamh/dist" BOOTSTRAP_VERSION="bootstrap-1.8" BOOTSTRAP_URI=" -amd64? ( ${BOOTSTRAP_DIST}/go-linux-amd64-${BOOTSTRAP_VERSION}.tbz ) -arm? ( ${BOOTSTRAP_DIST}/go-linux-arm-${BOOTSTRAP_VERSION}.tbz ) -arm64? ( ${BOOTSTRAP_DIST}/go-linux-arm64-${BOOTSTRAP_VERSION}.tbz ) -ppc64? ( + ${BOOTSTRAP_DIST}/go-linux-amd64-${BOOTSTRAP_VERSION}.tbz + ${BOOTSTRAP_DIST}/go-linux-arm-${BOOTSTRAP_VERSION}.tbz + ${BOOTSTRAP_DIST}/go-linux-arm64-${BOOTSTRAP_VERSION}.tbz ${BOOTSTRAP_DIST}/go-linux-ppc64-${BOOTSTRAP_VERSION}.tbz ${BOOTSTRAP_DIST}/go-linux-ppc64le-${BOOTSTRAP_VERSION}.tbz -) -s390? ( ${BOOTSTRAP_DIST}/go-linux-s390x-${BOOTSTRAP_VERSION}.tbz ) -x86? ( ${BOOTSTRAP_DIST}/go-linux-386-${BOOTSTRAP_VERSION}.tbz ) -amd64-fbsd? ( ${BOOTSTRAP_DIST}/go-freebsd-amd64-${BOOTSTRAP_VERSION}.tbz ) -x86-fbsd? ( ${BOOTSTRAP_DIST}/go-freebsd-386-${BOOTSTRAP_VERSION}.tbz ) -x64-macos? ( ${BOOTSTRAP_DIST}/go-darwin-amd64-${BOOTSTRAP_VERSION}.tbz ) -x64-solaris? ( ${BOOTSTRAP_DIST}/go-solaris-amd64-${BOOTSTRAP_VERSION}.tbz ) + ${BOOTSTRAP_DIST}/go-linux-s390x-${BOOTSTRAP_VERSION}.tbz + ${BOOTSTRAP_DIST}/go-linux-386-${BOOTSTRAP_VERSION}.tbz + ${BOOTSTRAP_DIST}/go-freebsd-amd64-${BOOTSTRAP_VERSION}.tbz + ${BOOTSTRAP_DIST}/go-freebsd-386-${BOOTSTRAP_VERSION}.tbz + ${BOOTSTRAP_DIST}/go-darwin-amd64-${BOOTSTRAP_VERSION}.tbz + ${BOOTSTRAP_DIST}/go-solaris-amd64-${BOOTSTRAP_VERSION}.tbz "
I think we have to download all of the bootstrap packages, unless there is another way to do this I don't know about. See bug #671394 and the following pull request: https://github.com/gentoo/gentoo/pull/10933
The issue with the arch use flags amd64, x86, etc. which I removed is that they are set to reflect the machine you are building *for*, not the machine doing the building. This was breaking a crossdev environment.A So, we either have big downloads or I start offering go-bin as a package and using the upstream go binary releases.
Can we add a comment to the ebuild (and a reference to this bug) so that one can lookup this information? Personally, I'm fine with downloading even those 500MB, should not be a problem these days. Thanks.
*** Bug 680860 has been marked as a duplicate of this bug. ***
Thank you William for the detailed information. I can live with it, should i close the ticket or keep it open for some time?
