Posted Jun 11, 2010 13:13 UTC (Fri) by farnz (guest, #17727)
[Link]
That doesn't reassure me any, I'm afraid. ksyscoca takes a bunch of text files under ${HOME}/.kde, and parses them into an efficient binary blob form that lives in /var/tmp. The KDE API for handling configurations keeps the binary blob and the text files in sync; if I edit the text files outside of the KDE API, I've invalidated the ksyscoca binary blob, and need to recreate it. KDE will do this automatically when I log in (based on mtimes, I assume), or I can blow away the binary blob, and still keep my settings unchanged.
The link you've given suggests that if I rebuilt my schemas, I'd lose my custom settings. That's a distinct retrograde step from ksyscoca, where if I wipe out my binary blob, I can rebuild with my existing settings from the text files; further, I can edit my settings with tools such as "vi" (useful in a broken-the-world scenario), blow away the binary blob, and have KDE rebuild the binary blob for me.