python-sdbus++: remove sdbus++ executable

When moving all packages over to use ${PYTHON_PN}-sdbus++ instead of
the (python2-based) sdbus++ alias, I ran into frequent problems where
BOTH python-sdbus++ and python3-sdbus++ were in the DEPEND-chain.  When
this happens, bitbake is upset because both packages install the sdbus++
executable.  (Both are in the DEPEND-chain because some packages have
transitioned to python3 and some have not.)

There are two reasons someone might depend on the python-sdbus++-native
package:

    1. They need to use the sdbus++ executable to generate code.
    2. They wrote their own scripts leveraging sdbus++'s module.

For #1, we can force everyone to use the python3 varient by adding
a DEPEND on python3-sdbus++-native and then removing sdbus++ (the
executable).  This will continue to install the python modules for #2.

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