On Wed, 2013-12-11 at 14:32 +0530, Gaurav Kalra wrote:
> [Gaurav wrote]
> >> While creating the key using vconftool, developer is expected to believe in
> >> relative paths but while setting up smack permissions, hir is expected to
> >> believe in absolute paths. This sounds more confusing to me.
> >
>
> [Casey wrote]
> > Right. I think that the problem is vconftool. We shouldn't need it. The
> > initial key files should be created when the package is built and installed
> > as part of the package. It should not be done as a post-op.
> >
>
>
> I agree to it.
>
> But AFAIK Tizen has witnessed plethora of debate around vconf and
> there must be reasons that vconftool still exists. (I wish I knew why
> it does)
vconf will be replaced in Tizen 3.0. It hasn't been replaced yet just
because the replacement tool hasn't landed yet. You should expect to
see porting of all tizen packages to use the new new in Q1.
--rusty
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
