particle-os/particle-os-modules
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(bling): Update documentation about dconf-update-service

Browse source
This commit is contained in:
fiftydinar 2024-10-02 10:14:33 +02:00 • committed by GitHub
parent 84285e8958
commit 562b6d6bfe
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 7 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

9
modules/bling/README.md
View file

@ -8,6 +8,11 @@ The bling to pull in is declared under `install:`, and the code for installing t
### `dconf-update-service`
The `dconf-update-service` submodule creates a systemd unit to automatically update changes you make to [dconf](https://wiki.gnome.org/Projects/dconf) in your custom image. For an example of a dconf keyfile, see the [dconf custom defaults documentation](https://help.gnome.org/admin/system-admin-guide/stable/dconf-custom-defaults.html.en).
The `dconf-update-service` submodule creates a systemd unit to automatically update changes you make to [dconf](https://wiki.gnome.org/Projects/dconf) in your custom image.
**Unlike the `gschema-overrides` module, dconf keyfiles are not checked at compile time**
For an example of a dconf keyfile, see the [dconf custom defaults documentation](https://help.gnome.org/admin/system-admin-guide/stable/dconf-custom-defaults.html.en).
Take a note that this documentation is for local-users, not for custom image maintainers. But it serves as a good example of what dconf file looks like.
Ignore the advice about creating the `user` profile, as it's already present & just place dconfs in `/etc/dconf/db/distro.d/`, not in `local.d` folder ([Thinking like a distribution](https://blue-build.org/learn/mindset/) mindset).
**Unlike the `gschema-overrides` module, dconf keyfiles are not checked at compile time for errors.**