tree 30b1d2e7311fa5f4b0769d7add2a63840500a6ea
parent 0bfc05be2d1fe89d2967b8939c2ff50d399236fe
author Andrew Geissler <geissonator@yahoo.com> 1687890833 -0500
committer Patrick Williams <patrick@stwcx.xyz> 1688571583 +0000

systemd: no installation in templated targets

Upstream yocto introduced a change via e510222 (systemd-systemctl:
fix instance template WantedBy symlink construction).

This fixes a bug that we in OpenBMC had been taking advantage of in that
we were able to document our templated target dependencies without it
actually doing anything. The real installation of services within
targets occurs in our bitbake recipes due to the complexity of chassis
and host instances on a per machine basis.

Leave the dependency information in the service files but comment them
out. It's useful to be able to look at a service and understand which
targets it's going to be installed into by the bitbake recipes.

The service files are already properly installed into the appropriate
targets by the recipe.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Idcb5458b6f2a3007c20f546604d4095650148803