* permission whitelists need to get placed on the same partition as the apps themselves
* check product and system individually and generate XMLs accordingly
Test: Verify missing entries for system and product get generated on hotdog
Test: Verify missing entries for system and system/product get generated on taimen and maple
Change-Id: I37bd5c7b738caaab93019688c6a944dc6bbffa75
Some applications declare their privileged permission as 'uses-permission-sdk-23(m)',
not 'uses-permission'. Adding '.*' to current regex expression to cover all the cases.
Test: python development/tools/privapp_permissions/privapp_permissions.py
Change-Id: I1ea8c9361bb53035481418631b34607ffecb238c
Signed-off-by: changho.shin <changho.shin@lge.com>
This was done largely so automation can make use of
privapp-permissions.xml generation.
Privapp_permissions.py no longer requires the build environment
to be setup. Instead, system files can be pulled from a connected
device, and aapt & adb can be set via the commandline. Otherwise,
they will default to the environment's default aapt/adb.
Priv-apps and the permission lists can be queried from the device
using command flags as well, removing the need for an Android
image to be built locally.
Bug: None
Test: Diff between previous privapp_permissions output and the
output for these changes was empty for the following runs:
./old_privapp_permissions.py
vs
./new_privapp_permissions.py [-d && -s SERIAL]
./new_privapp_permissions.py --aapt /path/to/aapt
./old_privapp_permissions.py /path/to.apk
vs
./new_privapp_permissions.py /path/to.apk
./new_privapp_permissions.py device:/path/to/apk
Change-Id: Ifaf35607d38c1d74111fd2f05628c0192fc791cb
