Hi all,
Following on from last month's CI kerfuffle I've followed through and
with some assistance from Daniel (iskunk) fully automated and optimised
the CI tarball generation outside of LUCI, with a focus on tarballs
for Linux distributions (though likely to be suitable for BSDs, too).
This has resulted in a name change for tarballs to reflect that they
are no longer intended to match upstream: ${VERSION}-linux.tar.xz.
From the next release, we'll begin publishing GitHub Releases for the
stable channel so that subscribers may receive email notifications.
Other channels may be added upon request (or we could trigger an email).
https://github.com/chromium-linux-tarballs/chromium-tarballs/
This closely follows the upstream packaging process. We even
using the same (or very slightly modified) scripts to do the work.
This enables us to ship significantly smaller tarballs. Since
distributions link against their own system libraries, and have
their own toolchains, we can exclude:
- Debian sysroot(s)
- Toolchain components (Rust, Clang, LLVM etc.)
- third_party/instrumented_libs
If there are any other obvious savings please do let us know, the
smaller tarballs are noticeably faster to unpack even on relatively
modern (and high-spec) systems.
We are hoping that these changes will be accepted into the '-lite'
tarballs upstream, as these are no longer significantly smaller
than the standard Chromium tarball.
Finally, I will be turning off the DigitalOcean Spaces CDN in a month.
Please switch to the Gentoo CDN if you haven't already:
https://chromium-tarballs.distfiles.gentoo.org/${VERSION}-linux.tar.xz
Please let me know if there are any problems by raising an issue
on the GitHub repo. Feature requests and PRs welcome!
Cheers,
Matt