summaryrefslogtreecommitdiffstats
path: root/meta-phosphor/recipes-phosphor/watchdog
diff options
context:
space:
mode:
authorLei YU <mine260309@gmail.com>2019-03-14 13:29:07 +0800
committerAndrew Geissler <geissonator@yahoo.com>2019-03-20 21:56:53 -0500
commitf33c69ca1546765da370dea09f53fa4cadf18d0c (patch)
tree85fb6d3aa579393d67cae388a66e78e8b0205d24 /meta-phosphor/recipes-phosphor/watchdog
parent806405f3f41f8e9fe42a06a18c299de702a83d78 (diff)
downloadtalos-openbmc-f33c69ca1546765da370dea09f53fa4cadf18d0c.tar.gz
talos-openbmc-f33c69ca1546765da370dea09f53fa4cadf18d0c.zip
obmc-phosphor-systemd: allow systemd unit from repo
If a recipe inherits obmc-phosphor-systemd, all the systemd units defined in the recipe shall exist in the code tree, otherwise it reports "Did not find unit file" error. This commit changes the behavior, and do not report the error if a unit does not exist in code tree. This allows the system unit to be installed from repo, as long as the repo does install the systemd unit to expected path. Tested: Verify the below case passes the build and the unit is installed correctly in the built image: * Put a systemd unit in repo; * In repo, install the unit into /lib/systemd/system * The repo's recipe defines SYSTEMD_SERVICE_${PN} without putting the unit in openbmc tree And verify if the systemd unit in repo is not installed, the build fails due to missing the unit. (From meta-phosphor rev: 5f56aaf1204a39035da1a493a97e86a73650000f) Change-Id: I9ec9c188357c2995d3e8ddbf2675c60f5e17560e Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-phosphor/recipes-phosphor/watchdog')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud