Bug fix release. OTPClient no longer aborts at startup when GLib finds a settings schema
left over from an older release, and staged package installs no longer generate system caches.
There is no on-disk format change; existing databases open unchanged.
- FIX: an outdated compiled settings schema found ahead of the current one, for example
under ~/.local/share or /usr/local/share, made the application abort at startup. It now starts
with default settings and logs a warning that names the missing keys and the directory holding
the outdated schema
- FIX: installing into a staging directory with DESTDIR no longer writes a compiled schema
and an icon cache that cover only OTPClient's files and clash with the ones owned by GLib
and the icon theme. A direct install still refreshes both, and the new POST_INSTALL_CACHES
build option turns the step off
- TEST: the application and the settings helper are started against a schema that lacks
the newest key and must not abort