mirror of
https://git.proxmox.com/git/fwupd
synced 2025-08-05 07:00:30 +00:00
![]() Instead of using RequiresMountsFor=/snap/fwupd/current, which will not work since /snap/fwupd/current is a symlink [1]. This will work since the mount units generated by snapd all have Before=snapd.service, so will be stopped after snapd.service during shutdown. With After=snapd.service, fwupd-activate.service will then stop before snapd.service, at a point when all snap mount units are still running. Fixes the issue where fwupd-activate.service hangs when stopped, causing a stop job timeout during shutdown. [1] See https://github.com/systemd/systemd/issues/8907 Closes #1654 |
||
---|---|---|
.. | ||
activate-shutdown | ||
fix-bash-completion | ||
fwup-efi-signed | ||
libefivar-fixpkgconfig | ||
update-mime | ||
dfu-tool.wrapper | ||
fwupd-command | ||
fwupd.wrapper | ||
fwupdmgr.wrapper | ||
fwupdtool.wrapper | ||
README.md | ||
snapcraft-master.yaml |
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.