Owain Davies wrote:
Hi,
I have written a custom system service that is instantiated by the
SystemServer and registered with the ServiceManager. This worked fine in
4.4.4 but having moved to 5.0.2 I see that I need to add entries in to
the service_contexts file. I have successfully managed this by modifying
external/sepolicy/service_contexts.
I am trying to keep my modifications very loosley coupled from the aosp
source tree. All the code is in a separate JAR, which is included in the
bootstrap class path with a PRODUCT_BOOT_JARS. Can I do the same for the
sepolicy modification to service_context. I have seen the
BOARD_SEPOLICY_UNION options but this would not be a board level change.
Is there something like a PRODUCT_SEPOLICY_UNION option?
Google did not like the idea of PRODUCT_SEPOLICY_*:
https://android-review.googlesource.com/#/c/44550/
If not how would you suggest I go about doing that?
The current guidance is to make a device tree per product and inherit
from the main device, this is how tuna, maguro, etc use to work.
Since our main focus is building policies we made a separate build
system that allows unioning/replacement at any level:
https://bitbucket.org/quarksecurity/build-policies
Thanks,
Owain
_______________________________________________
Seandroid-list mailing list
[email protected]
To unsubscribe, send email to [email protected].
To get help, send an email containing "help" to
[email protected].
_______________________________________________
Seandroid-list mailing list
[email protected]
To unsubscribe, send email to [email protected].
To get help, send an email containing "help" to
[email protected].
