855550 - Manifest munging tools should work with includes

Status: RESOLVED WORKSFORME

(Release Engineering :: General, defect)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

In bug 847351, we're trying to simplify how our manifests are organized.  Instead of specifying one manifest per device, we're going to start sharing portions of the manifest between devices.

I don't know how the releng manifest munging scripts work, so this bug could be nothing more than a heads up.

Vasil has already landed the change [1] to gonk-misc.  With this change, the manifest that is fetched from b2g-manifest is flattened into the one we install to sources.xml.  This same script is used by code-drop.sh [2] to create the sources.xml file that's stored in a code-drop (a.k.a snapshot).

If all of your manifest munging is done on the /system/source.xml file or the manifest included in a snapshot, nothing should be needed here.  If you guys are munging raw b2g-manifests, you'll need to update your tooling to deal with includes.  Please see [1] as a basis for changes (if you are using Python's minidom).



[1]https://github.com/mozilla-b2g/gonk-misc/commit/5256c656a3fc24ce67a1c48ad1dab514901bbc7b
[2]https://github.com/mozilla-b2g/B2G/blob/master/scripts/code-drop.sh

Comment 1

[Chris AtLee [:catlee]]

Thanks for the heads up. I believe this will work with our existing snapshot process as we process the sources.xml created by code-drop.sh.

Future support snapshot-less builds will handle this as well.