mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-20 16:55:40 +00:00
d1b2f93802
As described in changeset c94e87a18096, chrome manifest entries are reordered and don't necessarily appear in the order they have in jar.mn. And in some cases, the order does matter: when entries with flags are followed by entries with more broad flags or no flags at all. Nobody should be writing entries in that order on purpose, so error out during packaging when we detect the pattern. --HG-- extra : rebase_source : d9617bbcbd8560503c532a13c10c8afb0fd49411 |
||
---|---|---|
.. | ||
__init__.py | ||
flags.py | ||
manifest.py |