-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chromium tarball is much too big: split source? #763
Comments
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? |
https://groups.google.com/a/chromium.org/g/chromium-packagers/c/oE60kVFFMyQ/m/xxF0DCnkAQAJ seems interesting:
I assume we don't want to actually use these third-party tarballs in our recipe, but maybe the
|
https://chromium-review.googlesource.com/c/chromium/tools/build/+/6072713 has landed, and this already affect the latest releases. e.g. https://storage.cloud.google.com/chromium-browser-official/chromium-131.0.6778.139-lite.tar.xz is only 1.9 GB. I'll give building with that a try. @rakuco if that works, should we switch to the lite tarballs? |
Hm, it seems there are some licenses missing in the lite tarball:
The It seems this part of |
Issue is at https://issues.chromium.org/issues/384781867, and CL to fix it at https://chromium-review.googlesource.com/c/chromium/tools/build/+/6105714. |
CL landed and seems to have fixed the issue, but there's no new 131 tarball yet. We should try again once there is, or maybe as part of the next update. |
@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?
The text was updated successfully, but these errors were encountered: