mirror of
https://git.proxmox.com/git/fwupd
synced 2025-08-03 21:35:58 +00:00
ebbb13c2b4
In Fedora the only user of libfwupdate is fwupd and the fwupdate command line tool. It makes sense to absorb the libfwupdate library interface into the uefi plugin in fwupd. Benefits I can see include: * fwupd and fwupdate are very similar names; a lot of OEMs are confused * fwupd already depends on efivar for other things * We are maintaining an artificial library interface * The CI and translation hooks are already in place for fwupd * We don't need to check for features or versions in fwupd, we can just develop the feature (e.g. BGRT) all in one place. |
||
|---|---|---|
| .. | ||
| fix-bash-completion | ||
| fwup-efi-signed | ||
| libefivar-fixpkgconfig | ||
| update-mime | ||
| fwupdtool.wrapper | ||
| README.md | ||
| snapcraft-master.yaml | ||
| snapcraft-stable.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.