meta-openpower: Fix explicit dependencies antipattern

Out of the box bitbake examines built applications, automatically adds
runtime dependencies and thus ensures any library packages dependencies
are automatically added to images, sdks, etc.  There is no need to list
them explicitly in a recipe.

Dependencies change over time, and listing them explicitly is likely
prone to errors - the net effect being unnecessary shared library
packages being installed into images.

Consult
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-RDEPENDS
for information on when to use explicit runtime dependencies.

Change-Id: I29b9e86449c9e250b31a1f2a5e04b33ee27fd829
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
6 files changed
tree: 763ab28ab39e186b644d0c79b4249f32945af9b2
  1. classes/
  2. conf/
  3. recipes-bsp/
  4. recipes-phosphor/
  5. COPYING.apache-2.0
  6. COPYING.MIT
  7. LICENSE
  8. MAINTAINERS
  9. README.md
README.md

OpenPOWER

meta-openpower is the OpenPOWER layer and should be included in all OpenPOWER systems' bblayers.conf. More information on OpenPOWER can be found here.