Inline.

> -----Original Message-----
> From: Rees, Kevron [mailto:[email protected]]
> Sent: Thursday, November 21, 2013 3:21 PM
> To: Yoonsoo Kim
> Cc: [email protected]
> Subject: locale wet plugin
>
>
>
> On Wednesday, November 20, 2013, Yoonsoo Kim wrote:
> Inline too.
>
> > -----Original Message-----
> > From: Rees, Kevron [mailto:[email protected]]
> > Sent: Thursday, November 21, 2013 3:42 AM
> > To: Yoonsoo Kim
> > Cc: [email protected]
> > Subject: Re: [Dev] locale wet plugin
> >
> > inline
> >
> >
> > On Tue, Nov 19, 2013 at 8:22 PM, Yoonsoo Kim <[email protected]>
> > wrote:
> > > Kevron,
> > >
> > > There is a separate kinda general privilege for setting system-wide key:
> > > http://tizen.org/privilege/setting
> >
> > If I'm not mistaken (correct me if I'm wrong), but privileges are
> > tightly correlated with the actual wrt-plugin.  Meaning, the privilege
> > and so that provides that privilege are inseparable.  I cannot provide
> > another plugin that provides this privilege if one already exists.
> > Doing so might result in ambiguous behavior if it will even work at
> > all.
> >
> I don't know why each privilege is tightly correlated with the actual
> wrt-plugin. I'll look into the design. Basically feature and privilege are
> different concepts. So there is no reason each privilege should be tightly
> correlated with a wrt-plugin, that is, a feature.
>
> if it is possible that multiple plugins can provide the same feature and the
> system is smart enough to pick the right one, then using the existing 
> settings
> privilege would probably be fine.
>
I think that the locale setting feature is not specific to IVI. So I recommend 
you to implement the locale setting feature the existing wrt-plugin for system 
setting. Please, start the ACR process which you can find out at 
https://wiki.tizen.org/wiki/API_Change_Request_Review_Process

> For the other ivi-specific features/plugins, Rusty's suggestion would
> work.  Have wrt-security use a default core policy then look for other 
> policies
> that can be placed by other packaging.  Kinda like a /etc/policy.d/ type
> pattern.
>
Agreed. I and my colleagues started working on this.

BR,
Yoonsoo

> BR
> Kevron
>


_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to