| Message ID | 3e5105055d34dba87452f15213018d07e44e03f7.1374772012.git.paul.eggleton@linux.intel.com |
|---|---|
| State | Accepted |
| Commit | aea9d379ea217c78b64a81853ec3744188158008 |
| Headers | show |
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass index 380ed8e..cf02f88 100644 --- a/meta/classes/image.bbclass +++ b/meta/classes/image.bbclass @@ -132,6 +132,7 @@ python () { pn = d.getVar('PN', True) runtime_mapping_rename("PACKAGE_INSTALL", pn, d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", pn, d) + runtime_mapping_rename("BAD_RECOMMENDATIONS", pn, d) # Ensure we have the vendor list for complementary package handling ml_vendor_list = ""
Use runtime remapping on BAD_RECOMMENDATIONS just as we do with variables such as IMAGE_INSTALL, so that we're specifying the name prior to any renaming e.g. that done by debian.bbclass. Note that this is a change in behaviour for renamed packages, however this is the correct thing to be doing; a search of existing layers suggests this shouldn't cause widespread incompatibilities. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> --- meta/classes/image.bbclass | 1 + 1 file changed, 1 insertion(+)