diff options
| author | Todd Kennedy <toddke@google.com> | 2017-11-06 14:45:53 -0800 |
|---|---|---|
| committer | Todd Kennedy <toddke@google.com> | 2017-11-22 15:39:04 +0000 |
| commit | 232d29e0cdfd906da6b23c328c132bfc30607142 (patch) | |
| tree | 7952e6c973962998987a0d76013eca8ae5c2906b /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | d7f98747b37882c9e0821287d8dfa43f72e8c95f (diff) | |
Make sense out of scan & parse flags
Parse flags are often used confusingly to control policy during
APK parsing. Additionally, some flags [such as PARSE_IS_PRIVILEGED
or PARSE_IS_SYSTEM] aren't always determined based upon APK location
[they change based upon which apps are installed]. This means we
have to perform some gymnastics to set them correctly _before_
parsing a package.
Instead, these should be scan flags that can be determined at a
later point during package parsing. Then, based upon the scan flag
we apply policy on the package object to create the resulting
data structures.
Bug: 63539144
Bug: 69663125
Test: Manual; it builds, runs and applications can be installed / removed
Test: bit FrameworksServicesTests:com.android.server.pm.
Change-Id: I53fb18e58544e0a39f35eb6fb53c950e5c696aee
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions