Re: [Registry] array handling

[Markus R. <el...@ma...>]

Hello,

Am Freitag, 13. Februar 2015 schrieb Kai-Uwe Behrmann:
> That is implemented.

ksCut+ksSize works of course, too.

> > When software A is purged (i.e. its configuration should be removed)
> > there is  no obvious way to detect which entries were added during
> > installation (especially if the administrator alters parts of it). We
> > could do reference counting in meta data, but I am not really happy with
> > that.
> 
> A read time stamp, alias atime, would help. But that might be expensive
> depending how it is implemented.

The question to be answered is if any application that uses the configuration 
is installed. So atime does not really help: purging also removes 
configuration that was looked at; even modified configuration should be 
removed when software is purged.

> > Another problem is if something is expected to be an array but in fact is
> > not.  Currently, yajl has undefined behaviour if something starts with
> > #0 but is not an array and applications have problems, too. But thats
> > basically only another reason why configuration files must be validated.
> > Users always can write garbage in configuration files, thats a
> > fundamental problem unrelated to arrays.
> 
> Well, I rely on elektra to take care of that sort of issues :-)

That is our plan!

best regards,

-- 
Markus Raab            http://www.libelektra.org
Technische Universität Wien       el...@ma...
Institut für Computersprachen           Phone: (+431) 58801/185185
Argentinierstr. 8, 1040 Wien, Austria     FAX: (+431) 58801/18598

DVR 0005886