commit | cce26eb063488a4fe3403e55979cac7f8f6a7547 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Tue May 09 14:29:19 2023 -0500 |
committer | Adriana Kobylak <anoo@linux.ibm.com> | Mon May 15 20:29:24 2023 +0000 |
tree | 92f6f5fdf45f85b1d2f638591abd95b9f1976b7c | |
parent | d5e8e73b88f52acad408b8adfc7b9fdcc00fd860 [diff] |
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. Once the bump for this commit goes into openbmc/openbmc, I will ensure the recipe is updated to install all services correctly. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I401f988e92efb37f4928b14433b9d3035ec462d5
Phosphor BMC Code Management provides a set of system software management applications. More information can be found at Software Architecture
To build this package, do the following steps:
meson build
ninja -C build
To clean the repository run rm -r build
.