I'm not sure how strong of a problem this is anymore. It definitely was problematic early in fwupd's development, but fwupd-efi hasn't had any "ABI" impacting changes for a while now.
If there is a need to represent this from runtime, it would probably mean we need to actually install at runtime too (place in fwupd-unsigned instead).
I'm not sure how strong of a problem this is anymore. It definitely was problematic early in fwupd's development, but fwupd-efi hasn't had any "ABI" impacting changes for a while now.
Interesting point. There is a fwupd-efi.pc that will represent UEFI executable version (https:/ /github. com/fwupd/ fwupd-efi/ blob/main/ meson.build# L118). This is only used at build time in fwupd 1.6.0, and not consumed at runtime. So it was going to be installed into a build-deps only package fwupd-unsigned-dev (https:/ /github. com/fwupd/ fwupd-efi/ blob/main/ contrib/ debian/ fwupd-unsigned- dev.install)
If there is a need to represent this from runtime, it would probably mean we need to actually install at runtime too (place in fwupd-unsigned instead).