It seems like all we would need is a patch to the build system to alternatively accept elogind. HAVE_SYSTEMD should probably be renamed to HAVE_LOGIND in case the future brings further systemd support.
Alternatively, one could just add a consolekit USE flag, no matter whether logind is supported or not (not everyone is breaking out in hives at the thought of logging in as root).
That's not how this works.
Done upstream: https://github.com/hughsie/fwupd/pull/1040
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf627d629f87b6bb450c3d435b10176f3a653126 commit bf627d629f87b6bb450c3d435b10176f3a653126 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2019-02-25 10:57:21 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2019-02-25 12:01:18 +0000 sys-apps/fwupd: Add USE elogind Closes: https://bugs.gentoo.org/668522 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> sys-apps/fwupd/files/fwupd-1.2.4-elogind.patch | 105 ++++++++++++++++++++ sys-apps/fwupd/fwupd-1.2.4-r2.ebuild | 132 +++++++++++++++++++++++++ sys-apps/fwupd/metadata.xml | 3 +- 3 files changed, 239 insertions(+), 1 deletion(-)
This should have been added to fwupd-1.2.5 which was released just before adding elogind support.
Please open a separate bug regarding a version bump, it is not in the scope of this bug.
Done, see https://bugs.gentoo.org/678748