Support for building a revision mapping file with policy builds has been submitted for review at: https://bitbucket.org/seandroid/external-sepolicy/pull-request/14/initial-support-for-revision-mapping-file/diff https://bitbucket.org/seandroid/build/pull-request/2/add-sepolicy_version-to-product_packages/diff
The idea is to provide the ability to version the policy files without having to embed the version number into the files themselves. Possible uses are by updating clients that want to apply a policy. They may not want to apply the policy if the ramdisk is a higher version. Also, when a FOTA occurs, the ramdisk version may be higher than the one on /data, so logic in the choosing of which policy to load could be added to init, etc. Example code on how we can canonicalize the strings are in that code. See the pull requests for links to the sample code. -- Respectfully, William C Roberts
