os-release: switch python to variable expansion

The previous implementation of the OpenBMC os-release.bbappends
used a python function to inject `git` results into Python
variables.  Since the python function is then executed at multiple
task phases, it can result in the hash value changing between tasks,
which causes bitbake failures.

Rewrite the os-release implementation to use forced immediate
variable expansion, rather than a python function.  This, combined
with BB_DONT_CACHE, allows the variables to be expanded once at
recipe parse time and the values to continue through to the rest of
the task phases without affecting the hash.

Fixes openbmc/openbmc#3720.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iea2fd406f4e8b8843cdbcc8da4f2f29664344a27
1 file changed
tree: 58013118eb2ccdddf5ab1dc252effeea91f19eb9
  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.