meta-phosphor: Don't build debug tarball implicitly

In previous builds, the debug tarball was built as part of the
obmc-phosphor-image implicitly.  This increases the build times by a
trivial amount, which matters, but is not that important.  It also makes
debugging image dependencies (using bitbake -g) a bear, given that it
includes all dependencies for the debug tarball, as well as the actual
image.  Given that it's pretty trivial to build this manually via
bitbake obmc-debug-tarball
and (at least in my opinion) injecting the task seems like a bit of a
violation of the yocto intracacies, and gives a surprising result to the
user, this patchset removes the task add, and makes
obmc-phosphor-debug-tarball a truly separate build target.

Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Change-Id: I271ef5c313b12c4346b942a4818b90481312bbfe
1 file changed
tree: 713bd0f2cc4bc8747bc352779d1d22f2f8fba32f
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-graphics/
  10. recipes-phosphor/
  11. recipes-protocols/
  12. recipes-support/
  13. recipes-textproc/
  14. COPYING.apache-2.0
  15. COPYING.MIT
  16. LICENSE
  17. MAINTAINERS
  18. README.md
  19. 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.