189048b119
* chore: Remove usage of `yq` in favor of `jq` * fix: Missed bracket in `default-flatpaks` * fix: `get_json_array` complaining about unpopulated arrays * fix(files): Forgot to input `-r` flag for some `jq` calls * fix(gschema-overrides): Use `try` in `get_json_array` * chore(default-flatpaks): Replace `yq` with `jq` in run-time setup binaries * chore: Switch to simplified `jq` syntax without brackets * chore(default-flatpaks): Switch `repo-info` file from `yml` to `json` * fix(default-flatpaks): Some `yq` calls * chore: Revert back to bracket syntax for more reliable `jq` parsing * chore(files): Missed bracket syntax * chore: Approve bot suggestion about quoting Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update modules/files/files.sh Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * fix(yafti): Populating custom flatpaks It's populated in reverse order compared to the format in recipe, but it works * fix(fonts): Variable substitution is needed * fix: Typo * fix(fonts): Forgot to assign FONTS variable --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| installers | ||
| bling.sh | ||
| bling.tsp | ||
| dconf-update.service | ||
| module.yml | ||
| README.md | ||
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.