fwupd/contrib/snap
Mario Limonciello 44305bbde4 Rename EFI application from fwup<arch>.efi to fwupd<arch>.efi
This will prevent potentially clashing with fwupdate's EFI application
and allow them to remain co-installable.
2018-07-10 10:45:39 -05:00
..
fix-bash-completion trivial: snap: fix bash completion 2018-06-12 12:02:41 -05:00
fwup-efi-signed Rename EFI application from fwup<arch>.efi to fwupd<arch>.efi 2018-07-10 10:45:39 -05:00
libefivar-fixpkgconfig Add support for creating snaps 2018-05-31 14:12:06 -05:00
update-mime trivial: snap: Update the mime information 2018-06-06 17:37:37 -05:00
fwupdtool.wrapper trivial: snap: Update the mime information 2018-06-06 17:37:37 -05:00
README.md trivial: snap: Add a README 2018-06-04 12:01:27 -05:00
snapcraft-master.yaml Rename EFI application from fwup<arch>.efi to fwupd<arch>.efi 2018-07-10 10:45:39 -05:00
snapcraft-stable.yaml Rename EFI application from fwup<arch>.efi to fwupd<arch>.efi 2018-07-10 10:45:39 -05:00

Snap support

Snaps are containerised software packages that are simple to create and install. They auto-update and are safe to run. And because they bundle their dependencies, they work on all major Linux systems without modification.

stable vs unstable

Two yaml files are distributed:

  • snapcraft.yaml This uses tarball releases for all dependencies and what is currently in tree for fwupd.

  • snapcraft-master.yaml This uses git for most dependencies and may be considered unstable.

Building

Builds can be performed using snapcraft:

# snapcraft cleanbuild

Installing

A "classic" snap is produced, and locally built snaps can be installed like this:

# snap install fwupd_daily_amd64.snap --dangerous --classic

The --dangerous flag is because snaps built locally are not signed. Snaps distributed by a store will not need this flag.