Variant names are Fedora specific, so we should not depend on those in
shared manifests. Thus re-split the shared config into a shared
manifests for Kinoite and Kinoite Mobile.
We had previously enabled auto updates in Discover but we did not set an
update frequency. Kinoite is built daily but it is not necessary for
users to update that often. Set the update frequency to weekly to keep a
reasonable amount of time between updates while making sure that they
happen eventually.
Users may also manually update at anytime if they want updates to happen
faster or change the default in the system settings.
Flatpaks could (and maybe should) be updated faster (daily or every two
days) but we need support for that in Discover [1].
[1] https://bugs.kde.org/show_bug.cgi?id=454422
See: https://fedoraproject.org/wiki/Changes/KDEKinoiteAutoUpdateByDefault
Import packages from this group currently missing in Atomic Desktops. In
the future, we may rely on the comps group once we have cleaned it up.
Drop bcache-tools from kinoite-common. It is no longer (not sure if it
ever was) part of the anaconda-tools group.
See: https://gitlab.com/fedora/ostree/sig/-/issues/5
This package is explicitely not pulled via the comps group in order to
not be included by default in Fedora derivatives. We don't have a way to
signal that for Kinoite so include it here. Derivatives will have to
remove / disable the package as needed.
See: https://pagure.io/fedora-kde/SIG/issue/295
To be able to build images in the Fedora infrastructure with distinct
changes in the container vs classic ostree case, we need to split those
into a common manifest and a top level one that includes only the repos
and other distinct includes.
