When using the base keyword, it is once again possible to clean parts:
$ snapcraft clean <part-name>
Cleaning individual steps from a specific part, by adding
clean, is being redesigned to be more intuitive and straightforward in its use.
after keywords can now be used to order service launching within a snap.
The AppStream metadata extractor can now properly handle tags inside the relevant nodes and properly filter
Taking the following AppStream metadata as an example input:
<description> <p>List:</p> <p xml:lang="es">Lista:</p> <ul> <li>First item.</li> <li xml:lang="es">Primer item.</li> <li>Second item.</li> <li xml:lang="es">Segundo item.</li> </ul> </description>
…would generate the following desription in
List: - First item. - Second item.
Additionally, desktop files are now properly found from either the AppStream
launchable entries, or by falling back to legacy mode and inferring the desktop file from the appstream
The plugin can now use
build-snaps within the build environment. When any given
build-snaps entry exists for a part that uses the
cmake plugin, the plugin will make use of
CMAKE_FIND_ROOT_PATH so that libraries and headers from that snap are preferred.
cmake primitives are now used to drive the build instead of just calling
These features have already been used to create an initial set of KDE applications leveraging
core18 as a base as described on the KDE apps at the snap of your fingers article.
rust plugin has been refactored in a backwards compatible way to work better with the non-legacy
snapcraft with Homebrew for the first time, if
multipass is not found, the user will be prompted to install it before proceeding.
The issues and features worked on for 3.1 can be seen on the 3.1 launchpad milestone which are reflected in the following change list:
bashas a reserved package name on staging (#2423)
Last updated 1 year, 6 months ago. Help improve this document in the forum.