Make zucchini partial generation use our in-tree built zucchini executable
Categories
(Release Engineering :: General, task)
Tracking
(firefox146 fixed)
| Tracking | Status | |
|---|---|---|
| firefox146 | --- | fixed |
People
(Reporter: yannis, Assigned: yannis)
References
(Blocks 1 open bug)
Details
Attachments
(2 external files)
In bug 1919654, we landed a partials-zucchini task that generates partials by building and using the zucchini binary from upstream chromium. After the landing of bug 1950060 we will have our own binary generated from an in-tree vendoring. For compatibility reasons, partials-zucchini should use this binary rather than the one from upstream if possible.
Possible reasons for incompatibility include:
- desynchronization between the versions of Zucchini used by partials-zucchini and our in-tree vendoring;
- different choices in supported features, for example our in-tree vendoring will not support DEX because we don't plan to ship Android-related files as part of our updates, so if somehow (admittedly that is very unlikely) we were to generate a partial that contains a patch for a Dalvik executable, the patch generated by partials-zucchini would be unprocessable by
updater.exe.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
This lets us build the standalone zucchini binary without building all
Firefox, by using a mozconfig file containing:
ac_add_options --enable-project="tools/zucchini"
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
We stop relying on the chromium build system and tools, and instead
build the standalone zucchini binary directly from our own source tree.
This uses the tools/zucchini build project, to avoid having to build all
Firefox.
Comment 4•1 year ago
|
||
| bugherder | ||
Description
•