I added your patches on top of fwupd 2.0.20 and it builds fine for FreeBSD 15.0 but breaks building on FreeBSD 14.3. I am not sure if this was expected:

In D55590#1276134, @sergii.dmytruk_3mdeb.com wrote:

In D55590#1275939, @decke wrote:

Sorry that it took me so long and thanks a lot for your work, that looks really good to me!

I started looking at this issue some time ago but lost motivation because it was really hard to debug. So a really big tanks for fixing it!

Thank you for reviving and finalizing D29332 after it was abandoned!

Any comments on which way of handling libefivar is preferable? I.e., whether to add CONFLICTS = devel/efivar or make devel/efivar a dependency and add missing changes there (pointing at updated https://github.com/3mdeb/efivar could be simpler than adding a bunch of patches).

Sorry that it took me so long and thanks a lot for your work, that looks really good to me!

A update to properly build on FreeBSD 14 was committed some minutes ago. Don't break your hardware with it!

devel/efivar currently requires at least FreeBSD 14 (for 13.x it would require at least patches around qsort_r() and secure_getenv() (probably more after that))
sysutils/fwupd currently requires at least FreeBSD 15 (for 14.x it would need libinotify from ports (probably more after that))

This was a very productive EuroBSDCon DevSummit in Zagreb this year. fwupd is almost ready to be committed.