Add support enforcing all path requirements.
Setting PRODUCT_ENFORCE_ARTIFACT_PATH_REQUIREMENTS to be non-empty will verify that when an inherited product file makes an path requirement claim, no files other than the ones it produces are allowed inside its paths. This allows more rigorous control of what goes where, and specifically stops accidental inclusion of modules in the wrong places (which is very easy to do otherwise). In order to enable iterative improvements to current offenders, support for a whitelist is also added (via the new PRODUCT_ARTIFACT_PATH_REQUIREMENT_WHITELIST property). Verification is done that this variable corresponds to exactly the list of current offenders. Example use: PRODUCT_ENFORCE_ARTIFACT_PATH_REQUIREMENTS := true PRODUCT_ARTIFACT_PATH_REQUIREMENT_WHITELIST := system/priv-app/Dialer/Dialer.apk Bug: 80410283 Test: In a downstream CL specifying the above. Change-Id: I58047db08bde34da21759cfc55f398892b1c809a
Loading
Please register or sign in to comment