Open rwmacleod opened 10 months ago
The tarball publishing process upstream already creates a tarball called "chromium-lite" which removes some directories, but this list is not very up-to-date and actively maintained.
As a first step one could see if this tarball is considerably smaller than the one we use and whether one can actually build Chromium from it.
As for using LLVM and Rust from YP/OE and the rest of the suggestion: do you mean creating a tarball of our own?
@nrpt-m mentioned that with upstream adding Rust in chromium 117, the tarball is ~3 GB. Even before this, chromium-116.0.5845.187.tar.xz is 1.5 GB and 13 GB unpacked. It seemed hard to believe that all of that data would be required to build chromium. Using ncdu, the top level directories that are > 100 MiB are:
and the largest third-party componets are:
Is it possible to use llvm and rust from YP/OE and does anyone think that it would be a good idea to look at other large directories and remove them or split them into a seperate tarball if not needed. Does anyone object to such a change assuming that it's not too painful to implement and maintain?