Installing systemd specific files

Daiki Ueno dueno at
Mon Feb 27 16:32:38 UTC 2017


Roman Bogorodskiy <bogorodskiy at> writes:

> Currently p11-kit installs some systemd specific files:
>  - p11-kit-remote.socket
>  - p11-kit/p11-kit-remote.socket
>  - p11-kit/p11-kit-remote at .service
> and maybe something else I don't recall.
> As those are specific to systemd which only runs on Linux (AFAIK), I was
> thinking about disabling installation of these files on FreeBSD. I see
> two options:
>  - Detect if we're building for Linux and define something like
>    WITH_LINUX and install these files only if it's True
>  - More granular approach like adding configure arg '--with-systemd'
>    or somethings like that. I'm not sure, however, if that makes
>    much sense as it looks like most of the major distros have switched
>    over to systemd
> Which one is preferred?

I would prefer the latter; we could enable the option only if systemd is
installed, which can be checked with pkg-config.

By the way, those files are creating another problem on multilib

The problem is that the unit file contains arch-dependent path for, which is installed under $libdir.  We worked around
this on Fedora by splitting the package, but perhaps it might be still a
problem on other distributions.

One solution to this would be to add a dedicated command that exports
the proxy module, without specifying the path (e.g. p11-kit
remote-proxy).  However, since this systemd stuff is added for
NetworkManager, I would like to hear opinions from them.

Any thoughts?

Daiki Ueno

More information about the p11-glue mailing list