diff options
| author | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2019-03-22 21:41:12 -0400 |
|---|---|---|
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2019-03-26 16:46:21 -0400 |
| commit | ad06047d8c4db62a3d1b4af6a32bb11c2c7147ce (patch) | |
| tree | 1c5e31ad442a4462f9b3dbbb7e008fabff53455f /meta-portwell | |
| parent | e24a3fd2dfe1c687a4efc418d7fee3baf5fec283 (diff) | |
| download | talos-openbmc-ad06047d8c4db62a3d1b4af6a32bb11c2c7147ce.tar.gz talos-openbmc-ad06047d8c4db62a3d1b4af6a32bb11c2c7147ce.zip | |
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.
(From meta-openpower rev: 42fbcf6040860dc6b0b553febeabedd241f22a27)
Change-Id: If56c264d3807f604ae8ba9c948095ba61093285d
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-portwell')
0 files changed, 0 insertions, 0 deletions
