summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2014-08-19 13:43:18 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-08-25 08:57:45 +0100
commit1a76648ec99ec6051ef14ed2b251d1f92a090f3d (patch)
tree838020b042876307b124c0c37b049ced96981bf3
parentff6ab056c7f63387ef05c99840597bf644f47884 (diff)
downloadpoky-1a76648ec99ec6051ef14ed2b251d1f92a090f3d.tar.gz
package: Disable runtime mapping of RPROVIDES/RCONFLICTS/RREPLACES
It doesn't really make sense to run the remapping code on these variables. If specific renaming is needed, it should be applied manually. This means that the debian RPROVIDES of the original package name can be preserved. There was also a bug report about this on the OE-Core mailing list recently where someone else ran into this problem too. (From OE-Core rev: a0cd18ff5405b63b8296b8ef1fc2a488b906f576) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta/classes/package.bbclass3
1 files changed, 0 insertions, 3 deletions
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 1298758e13..0ff5370587 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -2021,7 +2021,4 @@ def mapping_rename_hook(d):
2021 runtime_mapping_rename("RDEPENDS", pkg, d) 2021 runtime_mapping_rename("RDEPENDS", pkg, d)
2022 runtime_mapping_rename("RRECOMMENDS", pkg, d) 2022 runtime_mapping_rename("RRECOMMENDS", pkg, d)
2023 runtime_mapping_rename("RSUGGESTS", pkg, d) 2023 runtime_mapping_rename("RSUGGESTS", pkg, d)
2024 runtime_mapping_rename("RPROVIDES", pkg, d)
2025 runtime_mapping_rename("RREPLACES", pkg, d)
2026 runtime_mapping_rename("RCONFLICTS", pkg, d)
2027 2024