950684 - add version + packaging target for update tooling

Status: RESOLVED FIXED

(Firefox Build System :: General, defect)

Description

[[e-mail] (:bhearsum)]

Over in bug 770995 we've been talking about how to make it possible to create MARs out of band of the build process. One major complication that arose was making MARs of different versions (eg, manifest v1 vs v2, some future change to use a new diffing algorithm, etc.) - and making sure we don't end up with a reimplementation of the tools (that could have different bugs).

The solution we came up with was to use the in tree tools. Rather than requiring the update packaging machines to build them on their own, it would be much easier (and safer) to give them known good binaries. We should add the concept of a version, so that whenever any component changes we can bump that and package up a new version of the tools.

At least the following need to be included in the package:
* mar
* mbsdiff
* tools/update-packaging/{common.sh,make_full_update.sh,make_incremental_update.sh,unwrap_full_update.pl}

(We've talked about replacing some of the old shell scripts with Python, not 100% sure if that will happen yet though.)

I'm not exactly sure how we'd go about implementing this -- tools/update-packaging is its own "application" already (in that you can --enable-application=tools/update-packaging), but I don't think any of the packaging naming/logic in packager.mk/package-name.mk would work for it.

Comment 1

[Rail Aliiev [:rail]]

This is exactly what Funsize implements :)