Closed
Bug 855550
Opened 11 years ago
Closed 11 years ago
Manifest munging tools should work with includes
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jhford, Unassigned)
References
Details
(Whiteboard: [b2g])
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•11 years ago
|
||
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.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Whiteboard: [b2g]
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•