Add packageconfig for dbus-sensors

Break up the dbus-sensors applications into packages so that users can
select which ones they want installed on their system.  The default is
to install everything.

This so that applications that will never provide sensor data for a
platform won't be installed and started.  A few of the reasons they
wouldn't be needed is:
* Not all systems contain the hardware that the applications access,
  such as the PCH or PECI interface.
* A system may use other applications for some of the functionality.
  For example phosphor-hwmon or phosphor-regulators may provide sensors
  for the power related hardware.

Packages can be removed by specifying them in a PACKAGECONFIG_remove
statement in a .bbappend in the appropriate layer.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I7d01b81561e4897e5cb579f5b4a5c4f52f291bc7
1 file changed
tree: c768d0abe9d66130fff462eac58a0163ad79c1cf
  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.