session: Add custom dconf profile #90
Conversation
This causes the cosmic-session to have a separate writable dconf-database (while still inheriting the default user database). This will (partially) prevent issues such as pop-os/cosmic-epoch#1174 in the future, as other desktops won't pick up cosmic's dconf profile.
|
Why using dconf in the first place? This is the worst concept invented by GNOME guys, resembling Windows Registry for no good reason. This issue people complained in pop-os/cosmic-epoch#1174 is just one example of many that will come. Why not using text file just like KDE Plasma and LXQt do? It's much easier and reliable, not to mention it's lighter (it doesn't require any service, no extra package to read data, no specific application to visualize it). |
It's for settings to theme GTK apps, which is impossible to do without dconf. Cosmic itself doesn't rely on dconf for its own settings. |
I see. Thanks for the explanation :) |
This causes the cosmic-session to have a separate writable dconf-database (while still inheriting the default user database).
This will (partially) prevent issues such as pop-os/cosmic-epoch#1174 in the future, as other desktops won't pick up cosmic's dconf profile.
Note to packagers: The dconf profile is highly specific to POP!_OS, which it why it isn't picked up by our
Justfile. You are highly encouraged to provide your own.Pop!_OS doesn't have a default user-profile, which means the profile defaults to
user-db:user(see man 7 dconf). The contents of the cosmic profile should be:Failing to provide a cosmic profile file will cause the session to have a read-only dconf store.