On Fri, Sep 28, 2012 at 12:45 PM, rpcraig <rpcr...@tycho.ncsc.mil> wrote: > On 09/28/2012 03:43 PM, William Roberts wrote: >> On Fri, Sep 28, 2012 at 12:40 PM, rpcraig <rpcr...@tycho.ncsc.mil> wrote: >>> On 09/28/2012 01:47 PM, William Roberts wrote: >>>> On Fri, Sep 28, 2012 at 10:45 AM, rpcraig <rpcr...@tycho.ncsc.mil> wrote: >>>>> On 09/28/2012 01:42 PM, William Roberts wrote: >>>>>> I don't think we would enforce a sepolicy dir...some devices might be >>>>>> fine with just external/sepolicy so why would they need an empty dir >>>>>> to work, which they would have to stub with a file becuase a lot of >>>>>> RCS don't allow additions of empty dirs... >>>>>> >>>>>> I think we keep the default search path the same, but if someone does >>>>>> specify other dirs, we search there too, more like appending to your >>>>>> PATH variable, this begs the question, can we override too? >>>>>> >>>>>> >>>>>> >>>>> I guess I wasn't clear with the last email. My intention was to always >>>>> include external/sepolicy. >>>> Yeah always include it...I think of it as appending to a search path >>>> PRODUCT_SEPOLICY_DIRS >>>> >>> See if this set of patches seems reasonable. Notice that these are*not* >>> patches on top of the prior patches. >> Yes this looks nice...gets rid of those pesky includes too. >> > I'll give people some more time with this to see if it fits their > configuration scenarios. Then, possibly Monday, I'll make a push for > this on AOSP.
Sounds reasonable... -- Respectfully, William C Roberts -- This message was distributed to subscribers of the seandroid-list mailing list. If you no longer wish to subscribe, send mail to majord...@tycho.nsa.gov with the words "unsubscribe seandroid-list" without quotes as the message.
