os-release: only run bbappend on do_compile

Chasing an intermittent os-release build failure via
openbmc/openbmc#3720. Not clear if this fix will resolve
that issue but there does not appear to be any reason to
run the logic in the bbappend outside of the do_compile
step since that is the only place the OS_RELEASE_FIELDS
are utilized by the base recipe.

Change-Id: Iefaa3a16af7572f338a056115e2cabb463e74b7e
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: 04a490f78d620272850894b65bcffab83530d2a6
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.