I believe there are a few problems with systemd handling in sys-apps/bolt, especially 0.8. 1) The -Dsystemd= option you set in emesonargs doesn't do anything anymore since this commit: https://gitlab.freedesktop.org/bolt/bolt/commit/4f33281c98c92c1592d5810cb1aabca9b9d97ce9 Now it's just detecting presence of systemd (automagically) and using that to decide whether to install units. Do we need to patch the meson file to set a unitdir directly, not relying on systemd.pc? Not sure. 2) As far as I can see, nothing links to systemd libraries so I don't think the :0= dep is correct. You may even be able to remove the dep entirely, if we stop relying on systemd.pc to set the unitdir.
not seeing anything in sources that depends on systemd but contrib/bolt.spec.in depends on it :( I can agree on removing the :0= part at least. The automagic is annoying if you see a patch for it, let me know :D BuildRequires: pkgconfig(systemd) BuildRequires: pkgconfig(libsystemd) BuildRequires: systemd
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6870ec497edae69537ca8c54317ef03e91da04ad commit 6870ec497edae69537ca8c54317ef03e91da04ad Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2020-01-03 20:41:43 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2020-01-03 20:41:55 +0000 sys-apps/bolt: simplify systemd dependency Fixes: https://bugs.gentoo.org/699308 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> sys-apps/bolt/bolt-0.8.ebuild | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
