Re: at-spi2-core now needs libsystemd on Linux

Benny Siegert <[email protected]> writes:

> What is the correct way to solve this?
>
>  - try to make it not use libsystemd?

It seems many people consider systemd a bug and also that it is getting
worse:
  https://www.theregister.com/software/2026/03/24/age-checks-creep-into-linux-as-systemd-gets-a-dob-field/5229495

so if it can be made not to use it, as wiz@ points out, that seems best.

>  - add /usr/lib64/pkgconfig to the pkg-config search path?

This is a larger question that's fair to address separately, and it's
messy.   I assume you are talking about pkgsrc pkg-config.

On one hand pkgsrc pkg-config should search not only pkg-config in
$prefix, but also where the base system has things.  Someone migth be
using pkg-config outside of pkgsrc, e.g. to build something from
upstream vcs with pkgsrc deps.

On the other hand, bl3 wants to hide things are aren't buildlinked in,
so when used as part of a pkgsrc build random base things shouldn't be
found.

>  - add some kind of builtin.mk for libsystemd?

If we have a libsystemd package, and the base version is ok, then yes we
should have a builtin.mk.  But if we don't have a libsystemd package,
then this does not make sense.

>  - add a systemd package?

We could, or libsystemd, but it seems that if we can avoid it, that's
better.

My impression is that on operating systems (including "GNU/Linux
distributions"), many dislike systemd, to the point of choosing an OS
without it.  Installing systemd because some package casually depends on
it is thus probably a bug.