On Thu, 2013-11-21 at 14:34 +0900, Yoonsoo Kim wrote: <snip/> > > > > What would you suggest? We fork wrt-security in our profile? We have > > ivi-specific plugins. We cannot use these plugins without adding the > > correct <privilege...> section to our web app's wgt file. The wgt > > file will not install unless we add the privilege to the wrt-security > > package. I don't like how it works. I find the wrt-security package > > redundant with SMACK and now PolicyKit in place. But this is the only > > process by which we can enable our IVI-specific web APIs. > > > Now I understand what you mean. Wrt-security is configurable for > profile-specific privileges but privilege manager is not configurable for > each > profile. That's the problem you are facing. Let me think this problem for a > moment.
Instead of having just one policy file, what if we had the concept of the core tizen policy file and then enable a profile or OEM or Tier 1 to provide an additional policy file that acted as an overlay extending the set of items exposed? --rusty _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
