[Kde-pim] configuration in akonadi-next

[Aaron J. Seigo]

On Thursday, December 18, 2014 14.39:03 Daniel Vrátil wrote:
> Shipping a pre-configured sqlite database is much harder than shipping an
> INI file.

There is no reason (that I can think of) that we can't provide a populate-the-
sqlite-db-from-INI-files procedure that runs automagically on the client side. 
So this should be, with a small amount of effort, be a non-issue.

> > However, I believe that the config should indeed be rather stored in it's
> > own config file.
> > The reason is smaller overhead compared to starting and querying
> > KAccounts.
> 
> Also storing full configuration in (binary) database is evil and simply
> wrong
> :-)

"Text" files are binary files with nice editors, that's all. (... just look at 
one with a hexeditor ;)

Access, not format, is what matters. I think tdb does this just about 
perfectly. It has a binary format on disk for efficiency but provides a nice 
little editor.

Some configuration makes sense as text, some doesn't. But there is no 
(sensible) "all config should be text" rule.

-- 
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20141218/22c499eb/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/