tree 3b283f5fd0b58fd879d37b7319bf62108765c9f7
parent 7fb6c3460f9b6591cd7856cfcbc9945925e085b8
author Andrew Geissler <geissonator@yahoo.com> 1683580241 -0500
committer Adriana Kobylak <anoo@linux.ibm.com> 1683754766 +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.

In some cases, we had hard coded the target instance, which does install
the service correctly, but only in that one target. All services should
be installed via the bitbake recipe to ensure the service is properly
installed in all instances of the target (or service). Once the bump for
this commit goes into openbmc/openbmc, I will ensure the recipe is
updated to install all services correctly.

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