Yeah I don't think checkfc can be repurposed for this. On Jan 22, 2013 5:19 AM, "rpcraig" <[email protected]> wrote:
> On 01/21/2013 10:55 PM, William Roberts wrote: > > Just a hunch but does .* work? > On Jan 21, 2013 7:20 PM, "William Roberts" <[email protected]> > wrote: > >> I ran a property contexts file through checkfc to see what the result >> was and the only issue it has is expanding the * for default. If you >> comment that out and try to add a duplicate label, it properly detects >> these and dies. Should we re-purpose checkfc for this or write a >> custom tool for compile time checks? >> >> This is currently the only file going unchecked into the ramdisk >> during the build. >> >> Thoughts and comments are appreciated. >> >> -- >> Respectfully, >> >> William C Roberts >> > > .* will certainly silence checkfc but then the context backend for > labeling the property keys (label_android_property.c) would have to change. > Besides, all the property keys in Android are based on having a dotted > notation so letting .* be the default label sorta seems like its catching > just the keys that begin with a dot. Also, the backed logic for the > property context doesn't use regular expression mappings like file_contexts > does. So the .* is a bit misleading in this context. >
