dconf databases:
================
We have 4 databases.
  - A read only system database called "nemo" which is used to store configuration for packages coming from nemo.
  - A read only system database called "vendor". This allows vendors to override and customize stuff.
    An example is the theme. Nemo has its theme and the nemo database contains the name of it.
    A vendor (like Jolla can override it with its own theme and store that info in the vendor db).
  - A read only system database called "vendor-variant" which can be used if a vendor needs to produce multiple variants.
  - A read/write db called user which contains the configuration.

Configuration file which specifies the databases is stored in /etc/dconf/profile/user
  - user db is in: /home/nemo/.config/dconf/user
  - nemo db is in: /etc/dconf/db/nemo
  - vendor db is stored in /etc/dconf/db/vendor
  - vendor-variant db is stored in /etc/dconf/db/vendor-variant

Adding app specific defaults:
=============================
    - Create a key file with your defaults. You can check dconf documentation for an example https://developer.gnome.org/dconf/unstable/dconf-overview.html (Search for Key Files) or check /etc/dconf/db/nemo.d/
    - copy it to /etc/dconf/db/nemo.d/<package-name>.txt
    - call dconf-update via a oneshot (%{_bindir}/add-oneshot dconf-update) in %post.