My recommendation would be to: - Move <https://github.com/ublue-os/bluefin/blob/main/etc/dconf/db/l
My recommendation would be to:
- Move https://github.com/ublue-os/bluefin/blob/main/etc/dconf/db/local.d/01-ublue to
- Add
- Remove the
Benefits:
- No systemd service.
- Changes the defaults instead of writing to the local database. So nothing is left behind in dconf db after uninstalling a package.
- Same config format.
- Overrides is what everyone uses when they make distros. It's cleaner.
- We get validation of config overrides during the build. It prints warnings (the build still works since it isn't an error, but it tells us what's wrong and helps us catch it), like this:
- Move https://github.com/ublue-os/bluefin/blob/main/etc/dconf/db/local.d/01-ublue to
/usr/share/glib-2.0/schemas/ublue.gschema.override.- Add
glib-compile-schemas /usr/share/glib-2.0/schemas as the last scripted step of the image build process.- Remove the
dconf update systemd script: https://github.com/ublue-os/bluefin/blob/main/etc/systemd/system/dconf-update.serviceBenefits:
- No systemd service.
- Changes the defaults instead of writing to the local database. So nothing is left behind in dconf db after uninstalling a package.
- Same config format.
- Overrides is what everyone uses when they make distros. It's cleaner.
- We get validation of config overrides during the build. It prints warnings (the build still works since it isn't an error, but it tells us what's wrong and helps us catch it), like this:
"Override for key “flatpak” in schema “com.github.stunkymonkey.nautilus-open-any-terminal” in override file “/usr/share/glib-2.0/schemas/99_com.github.stunkymonkey.nautilus-open-any-terminal.gschema.override” is not in the list of valid choices; ignoring override for this key."
