Now that https://github.com/snapcore/snapcraft/pull/3596 has been
released in snapcraft 6.0.1, drop the prompt that tells users to
disconnect the old framework snap.
Also drop --enable-experimental-extensions from CI because kde-neon
has been declared stable for core20.
Open & save dialogs might fail if it is not running.
org.freedesktop.portal.Desktop is DBus activated and this doesn't play
nicely with AppArmor at the moment.
As per https://snapcraft.io/docs/snap-layouts,
bind-mounts significantly increase the startup time of the snap.
Use symlinks instead for better performance.
This prevents the config and the user collection from being
backed up by snapd on update. If the user reverts qelectrotech,
the current collection will thus not be overwritten by the
possibly outdated backup.
Add a migration script that automatically transfers the user's .qet
directory to the new location.
The kde-neon extension reduces our boilerplate in snapcraft.yaml
and reduces the snap size considerably, as we do not need to ship
any library that is already included in the kde-frameworks-5-core18
snap itself.
This limits qelectrotech builds to the architectures supported
by kde-frameworks-5-core18, i.e. only amd64.
This allows building the master branch of QElectroTech with a simple
command:
$ flatpak-builder _build build-aux/flatpak/org.qelectrotech.QElectroTech.json
The Linux and Windows packaging recipes don't have any restrictions on
where they have to be located. Snapcraft is the strictest on this.
Moving this to build-aux/ means we can have all the packaging recipes in
one place.
Snapcraft can find its build recipes in 2 places:
* a snap/ directory at the top of the sources;
* a build-aux/snap/ directory, since Snapcraft 3.3;
This commit moves from the former to the latter, so that we can group
all the packaging recipes together.
