Mastodon Skip to content

bling

The bling module can be used to pull in small “bling” into your image. Bling is stuff that doesn’t necessitate being configured at build time, in the form of configuration files or program installers.

The bling to pull in is declared under install:, and the code for installing them is all in simple named scripts under the installers/ directory. The basic code for the bling module is very similar to the code of the script module.

Submodule documentation

dconf-update-service

The dconf-update-service submodule creates a systemd unit to automatically update changes you make to dconf in your custom image.

For an example of a dconf keyfile, see the dconf custom defaults documentation.

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 mindset).

Unlike the gschema-overrides module, dconf keyfiles are not checked at compile time for errors.

Example configuration

type: bling
install:
- rpmfusion # install RPMFusion repos, including tainted repos & disable negativo17 repos if installed
- negativo17 # install negativo17 repos and set priority to 90, uninstall RPMFusion repos if installed
- ublue-update # https://github.com/ublue-os/ublue-update
- 1password # install 1Password (stable) and `op` CLI tool
- dconf-update-service # a service unit that updates the dconf db on boot
- gnome-vrr # enables gnome-vrr for your image

Configuration options

install: (required array)

List of bling submodules to run / things to install onto your system.

Possible values: rpmfusion, negativo17, ublue-update, 1password, dconf-update-service, gnome-vrr