Re: [PATCH v3 1/2] optee-client: use udev rule and systemd service from upstream

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Wed, Oct 23, 2024 at 02:22:30PM +0000, Tom Hochstein (OSS) wrote:
> Hi Mikko,
> 
> We have multilib testing that is failing now because the systemd folder is being installed in `libdir` instead of the non-arch-specific `systemd_system_unitdir = "${nonarch_base_libdir}/systemd/system"` as is codified in `bitbake.conf`.
> 
> ERROR: optee-client-4.4.0.imx-r0 do_package: QA Issue: optee-client: Files/directories were installed but not shipped in any package:
>   /usr/lib64/systemd
>   /usr/lib64/systemd/system
>   /usr/lib64/systemd/system/tee-supplicant@.service
> 
> I'm not sure how this should be fixed, as it doesn't appear that CMAKE can handle more than one libdir. Can the install of the service file be hard-coded to use /usr/lib? Or does this need to be fixed in the recipe?

As mentioned in https://github.com/OP-TEE/optee_client/issues/393
your use case is "sysvinit" without "usrmerge" in distro features.
"sysvinit" conflicts with "systemd" init.

These recipe changes only install the systemd service file if "systemd" is
enabled in DISTRO_FEATURES. Your usecase should be covered by that.

Cheers,

-Mikko