From a246af9bf76d6a06e6d5f371710e54944e007161 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Thu, 10 May 2012 09:24:22 +0100 Subject: package.bbclass: Drop EXPORT_FUNCTIONS use against mapping_rename_hook The usage of this function renaming and it being called using bb.build.exec_func() causes needless indirection loops, confusing log files and seems generally pointless. This simplification makes the process much simpler and faster. I can't come up with a good reason why the export_functions functionality is needed for this function. (From OE-Core rev: 74daad03ca29a03b0005f7d2b90a0347d5b583a5) Signed-off-by: Richard Purdie --- meta/classes/package.bbclass | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'meta/classes/package.bbclass') diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass index 44e551f6dd..3d0f406b80 100644 --- a/meta/classes/package.bbclass +++ b/meta/classes/package.bbclass @@ -1788,7 +1788,7 @@ addtask package_write before do_build after do_package # Helper functions for the package writing classes # -python package_mapping_rename_hook () { +def mapping_rename_hook(d): """ Rewrite variables to account for package renaming in things like debian.bbclass or manual PKG variable name changes @@ -1799,6 +1799,4 @@ python package_mapping_rename_hook () { runtime_mapping_rename("RPROVIDES", d) runtime_mapping_rename("RREPLACES", d) runtime_mapping_rename("RCONFLICTS", d) -} -EXPORT_FUNCTIONS mapping_rename_hook -- cgit v1.2.3-54-g00ecf