Hooking LOCAL_INIT_RC files

[William Roberts]

I would like to be able to post process all the init.rc files specified in a build so I can run tools on them to find stupid things that folks like to do and that are often tighter than any

of the current CTS checks, (perhaps some CTS tests for these wouldn't be a bad thing to add at some point).

I was wondering if there is a simple way I am missing to grab all these? Maybe set up a phony target that has a dependency on boot.img, system.img, vendor.img?