I would like to refactor the moz.yaml schema to support significantly more expressive updating steps. libdav1d and libaom are presently codified as [separate python](https://searchfox.org/mozilla-central/rev/9f074fab9bf905fad62e7cc32faf121195f4ba46/python/mozbuild/mozbuild/vendor_dav1d.py) [scripts](https://searchfox.org/mozilla-central/rev/9f074fab9bf905fad62e7cc32faf121195f4ba46/python/mozbuild/mozbuild/vendor_aom.py) and I'd like to convert these into pure-yaml updates. When I get that working, lt's look at the resulting yaml schema and see how confusing it is and if we want to land it. This bug will probably accumulate a fairly large patchset as I work towards that goal. The purpose of this is to make it easier to specify vendor in new libraries (by avoiding duplicating python logic) as well more easily support top-level vendor commands such as --check-for-update which would return an identifier of an update if available.
Bug 1637845 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I would like to refactor the moz.yaml schema to support significantly more expressive updating steps. libdav1d and libaom are presently codified as [separate python](https://searchfox.org/mozilla-central/rev/9f074fab9bf905fad62e7cc32faf121195f4ba46/python/mozbuild/mozbuild/vendor_dav1d.py) [scripts](https://searchfox.org/mozilla-central/rev/9f074fab9bf905fad62e7cc32faf121195f4ba46/python/mozbuild/mozbuild/vendor_aom.py) and I'd like to convert these into pure-yaml updates. When I get that working, let's look at the resulting yaml schema and see how confusing it is and if we want to land it. This bug will probably accumulate a fairly large patchset as I work towards that goal. The purpose of this is to make it easier to specify vendor in new libraries (by avoiding duplicating python logic) as well more easily support top-level vendor commands such as --check-for-update which would return an identifier of an update if available.