* fix(default-flatpaks): Always enable systemd services
Ensures that the module always removes Fedora Flatpaks, even if a
system-wide flatpak remote isn't configured for the module.
* chore(default-flatpaks): Add output for result of repo config
* fix(default-flatpaks): Better handle multiple uses of module
* chore(default-flatpaks): Add label to output of existing config
* docs(default-flatpaks): Mention that Flatpak remote can be re-configured
* docs(default-flatpaks): Add second example to README
* docs(default-flatpaks): Clarify repo config in second example
* docs(default-flatpaks): Make example config match other modules
* docs(default-flatpaks): Indent list items in example config
Does seem to work if they aren't indented, but this way matches other
modules and seems to be best practice
There's a lot of bling "submodules" that might require documentation. Including them inside the same README is beneficial, because it makes the appear on the ublue website too, and their documentation is often not that long.
* fix: terminology
* docs: mention ostree
this is *not* the case on all fedora distros, only the "immutable" / ostree ones
---------
Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com>
There won't be anything to remove unless the module is called more than once, and if it's called more than once, the user would expect every Flatpak to be in the respective lists, so there's no need to call rm -f on it.
* docs: chore: rn ":" from "Example configuration"
* docs: correct title casing for fonts module title
* docs: document OS_VERSION in example,...
non-copr example for rpmrepos
* docs: remove bling fonts option from bling example
* docs: start yafti README the same way as others
"The yafti module..."
