Skip to contentSkip to conversation

perf: fix issue about package splitting

PATCH Superseded Chong Lu 3 participants 9 messages Sep 3, 2014 – Sep 4, 2014

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore

Chong Lu

author
#0 lore raw

v2 cover perf: fix issue about package splitting

The following changes since commit 83ebcb1f0c6ec48c526d14324b3b2037f0f4fe43:

bitbake: process: Ensure abnormal exits set an error level (2014-09-02 18:10:37 +0100)

are available in the git repository at:

git://git.pokylinux.org/poky-contrib chonglu/perf
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=chonglu/perf

Chong Lu (1):
perf: fix issue about package splitting

 meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)
Signature · 1 line
1.9.1
author
#1 lore raw

PATCH v2 1/1 perf: fix issue about package splitting

Currently, perf can't split to perf-archive, perf-tests, perf-python and perf-perl. All files are included in perf package. Change the files paths to make split successfully and add PACKAGECONFIG to make main pkg depends on sub pkgs as default.

---
 meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)
meta/recipes-kernel/perf/perf.bb +12 -5
index bfd210c..baf0077 100644
@@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
 
 PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
 
+PACKAGECONFIG ??= "archive perl python tests"
+PACKAGECONFIG[archive] = ",,, ${PN}-archive"
+PACKAGECONFIG[perl] = ",,, ${PN}-perl"
+PACKAGECONFIG[python] = ",,, ${PN}-python"
+PACKAGECONFIG[tests] = ",,, ${PN}-tests"
+
 RDEPENDS_${PN} += "elfutils"
 RDEPENDS_${PN}-archive =+ "bash"
 RDEPENDS_${PN}-python =+ "bash python"
 RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
+RDEPENDS_${PN}-tests =+ "python"
 
 RSUGGESTS_SCRIPTING = "${@perf_feature_enabled('perf-scripting', '${PN}-perl ${PN}-python', '',d)}"
 RSUGGESTS_${PN} += "${PN}-archive ${PN}-tests ${RSUGGESTS_SCRIPTING}"
 
-FILES_${PN} += "${libexecdir}/perf-core ${exec_prefix}/libexec/perf-core ${libdir}/traceevent"
+FILES_${PN} += "${libdir}/traceevent"
 FILES_${PN}-dbg += "${libdir}/python*/site-packages/.debug"
-FILES_${PN}-archive = "${libdir}/perf/perf-core/perf-archive"
-FILES_${PN}-tests = "${libdir}/perf/perf-core/tests"
-FILES_${PN}-python = "${libdir}/python*/site-packages ${libdir}/perf/perf-core/scripts/python"
-FILES_${PN}-perl = "${libdir}/perf/perf-core/scripts/perl"
+FILES_${PN}-archive = "${exec_prefix}/libexec/perf-core/perf-archive"
+FILES_${PN}-tests = "${exec_prefix}/libexec/perf-core/tests"
+FILES_${PN}-python = "${exec_prefix}/libexec/perf-core/scripts/python"
+FILES_${PN}-perl = "${exec_prefix}/libexec/perf-core/scripts/perl"
 
 
 INHIBIT_PACKAGE_DEBUG_SPLIT="1"
Signature · 1 line
1.9.1
#2 lore raw
Quoted 19 lines · Chong Lu

Currently, perf can't split to perf-archive, perf-tests, perf-python and perf-perl. All files are included in perf package. Change the files paths to make split successfully and add PACKAGECONFIG to make main pkg depends on sub pkgs as default.

---
 meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)
meta/recipes-kernel/perf/perf.bb +1 -0
index bfd210c..baf0077 100644
@@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
 
 PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
 
+PACKAGECONFIG ??= "archive perl python tests"

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 162

Quoted 10 lines
meta/recipes-kernel/perf/perf.bb +6 -0
+PACKAGECONFIG[archive] = ",,, ${PN}-archive"
+PACKAGECONFIG[perl] = ",,, ${PN}-perl"
+PACKAGECONFIG[python] = ",,, ${PN}-python"
+PACKAGECONFIG[tests] = ",,, ${PN}-tests"
+
 RDEPENDS_${PN} += "elfutils"
 RDEPENDS_${PN}-archive =+ "bash"
 RDEPENDS_${PN}-python =+ "bash python"
 RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
+RDEPENDS_${PN}-tests =+ "python"

I now realise the trick you're playing with PACKAGECONFIG here. Instead can we just define a package (say ${PN}-all but I'll accept a better name) which has dependencies on archive perl python tests so then the user can choose ${PN}, ${PN}-all or some other combination depending on their needs?

Quoted 4 lines
meta/recipes-kernel/perf/perf.bb +0 -1
 RSUGGESTS_SCRIPTING = "${@perf_feature_enabled('perf-scripting', '${PN}-perl ${PN}-python', '',d)}"
 RSUGGESTS_${PN} += "${PN}-archive ${PN}-tests ${RSUGGESTS_SCRIPTING}"
 
-FILES_${PN} += "${libexecdir}/perf-core ${exec_prefix}/libexec/perf-core ${libdir}/traceevent"

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 172

Quoted 10 lines
meta/recipes-kernel/perf/perf.bb +5 -4
+FILES_${PN} += "${libdir}/traceevent"
 FILES_${PN}-dbg += "${libdir}/python*/site-packages/.debug"
-FILES_${PN}-archive = "${libdir}/perf/perf-core/perf-archive"
-FILES_${PN}-tests = "${libdir}/perf/perf-core/tests"
-FILES_${PN}-python = "${libdir}/python*/site-packages ${libdir}/perf/perf-core/scripts/python"
-FILES_${PN}-perl = "${libdir}/perf/perf-core/scripts/perl"
+FILES_${PN}-archive = "${exec_prefix}/libexec/perf-core/perf-archive"
+FILES_${PN}-tests = "${exec_prefix}/libexec/perf-core/tests"
+FILES_${PN}-python = "${exec_prefix}/libexec/perf-core/scripts/python"
+FILES_${PN}-perl = "${exec_prefix}/libexec/perf-core/scripts/perl"

Can we use ${libexecdir} here please rather than hardcode it?

Cheers,

Richard

author
#3 lore raw
Quoted 19 lines · Richard Purdie
Quoted 18 lines · Chong Lu

Currently, perf can't split to perf-archive, perf-tests, perf-python and perf-perl. All files are included in perf package. Change the files paths to make split successfully and add PACKAGECONFIG to make main pkg depends on sub pkgs as default.

---
  meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
  1 file changed, 12 insertions(+), 5 deletions(-)
meta/recipes-kernel/perf/perf.bb +0 -0
index bfd210c..baf0077 100644
@@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
 
  PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
 
Quoted 16 lines

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 162

Quoted 11 lines
meta/recipes-kernel/perf/perf.bb +7 -0
+PACKAGECONFIG ??= "archive perl python tests"
+PACKAGECONFIG[archive] = ",,, ${PN}-archive"
+PACKAGECONFIG[perl] = ",,, ${PN}-perl"
+PACKAGECONFIG[python] = ",,, ${PN}-python"
+PACKAGECONFIG[tests] = ",,, ${PN}-tests"
+
  RDEPENDS_${PN} += "elfutils"
  RDEPENDS_${PN}-archive =+ "bash"
  RDEPENDS_${PN}-python =+ "bash python"
  RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
+RDEPENDS_${PN}-tests =+ "python"

I now realise the trick you're playing with PACKAGECONFIG here. Instead can we just define a package (say ${PN}-all but I'll accept a better name) which has dependencies on archive perl python tests so then the user can choose ${PN}, ${PN}-all or some other combination depending on their needs?

OK, I will put archive perl python and tests in ${PN}-full.

Quoted 4 lines
Quoted 4 lines
meta/recipes-kernel/perf/perf.bb +0 -0
  RSUGGESTS_SCRIPTING = "${@perf_feature_enabled('perf-scripting', '${PN}-perl ${PN}-python', '',d)}"
  RSUGGESTS_${PN} += "${PN}-archive ${PN}-tests ${RSUGGESTS_SCRIPTING}"
 
Quoted 12 lines

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 172

Quoted 11 lines
meta/recipes-kernel/perf/perf.bb +5 -5
-FILES_${PN} += "${libexecdir}/perf-core ${exec_prefix}/libexec/perf-core ${libdir}/traceevent"
+FILES_${PN} += "${libdir}/traceevent"
  FILES_${PN}-dbg += "${libdir}/python*/site-packages/.debug"
-FILES_${PN}-archive = "${libdir}/perf/perf-core/perf-archive"
-FILES_${PN}-tests = "${libdir}/perf/perf-core/tests"
-FILES_${PN}-python = "${libdir}/python*/site-packages ${libdir}/perf/perf-core/scripts/python"
-FILES_${PN}-perl = "${libdir}/perf/perf-core/scripts/perl"
+FILES_${PN}-archive = "${exec_prefix}/libexec/perf-core/perf-archive"
+FILES_${PN}-tests = "${exec_prefix}/libexec/perf-core/tests"
+FILES_${PN}-python = "${exec_prefix}/libexec/perf-core/scripts/python"
+FILES_${PN}-perl = "${exec_prefix}/libexec/perf-core/scripts/perl"

Can we use ${libexecdir} here please rather than hardcode it?

I checked environment, the variable libexecdir is "/usr/lib/perf". If I use this variable, package can't be split successfully.

Best Regards
Chong

Quoted 8 lines

Cheers,

Richard

author
#4 lore raw
Quoted 36 lines · Chong Lu
Quoted 25 lines · Richard Purdie
Quoted 24 lines · Chong Lu

Currently, perf can't split to perf-archive, perf-tests, perf-python and perf-perl. All files are included in perf package. Change the files paths to make split successfully and add PACKAGECONFIG to make main pkg depends on sub pkgs as default.

---
  meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
  1 file changed, 12 insertions(+), 5 deletions(-)
meta/recipes-kernel/perf/perf.bb +5 -0
index bfd210c..baf0077 100644
@@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
    PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
  +PACKAGECONFIG ??= "archive perl python tests"
+PACKAGECONFIG[archive] = ",,, ${PN}-archive"
+PACKAGECONFIG[perl] = ",,, ${PN}-perl"
+PACKAGECONFIG[python] = ",,, ${PN}-python"
+PACKAGECONFIG[tests] = ",,, ${PN}-tests"
+
  RDEPENDS_${PN} += "elfutils"
  RDEPENDS_${PN}-archive =+ "bash"
Quoted 8 lines

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 162

Quoted 3 lines
meta/recipes-kernel/perf/perf.bb +1 -0
  RDEPENDS_${PN}-python =+ "bash python"
  RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
+RDEPENDS_${PN}-tests =+ "python"

I now realise the trick you're playing with PACKAGECONFIG here. Instead can we just define a package (say ${PN}-all but I'll accept a better name) which has dependencies on archive perl python tests so then the user can choose ${PN}, ${PN}-all or some other combination depending on their needs?

Quoted 1 line

OK, I will put archive perl python and tests in ${PN}-full.

Sorry, I don't think we should use a pkg include four sub pkgs.
We have perf_feature_enabled to control whether enable perl and python, so it is hard to use feature if we put four sub pkgs in one pkg.

Best Regards
Chong

Quoted 33 lines
Quoted 10 lines
Quoted 10 lines
meta/recipes-kernel/perf/perf.bb +0 -0
  RSUGGESTS_SCRIPTING = "${@perf_feature_enabled('perf-scripting', 

'${PN}-perl ${PN}-python', '',d)}"
RSUGGESTS_${PN} += "${PN}-archive ${PN}-tests ${RSUGGESTS_SCRIPTING}" -FILES_${PN} += "${libexecdir}/perf-core
${exec_prefix}/libexec/perf-core ${libdir}/traceevent"

meta/recipes-kernel/perf/perf.bb +1 -2
+FILES_${PN} += "${libdir}/traceevent"
  FILES_${PN}-dbg += "${libdir}/python*/site-packages/.debug"
-FILES_${PN}-archive = "${libdir}/perf/perf-core/perf-archive"
-FILES_${PN}-tests = "${libdir}/perf/perf-core/tests"
Quoted 8 lines

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 172

Quoted 7 lines

-FILES_${PN}-python = "${libdir}/python*/site-packages ${libdir}/perf/perf-core/scripts/python"

meta/recipes-kernel/perf/perf.bb +4 -1
-FILES_${PN}-perl = "${libdir}/perf/perf-core/scripts/perl"
+FILES_${PN}-archive = "${exec_prefix}/libexec/perf-core/perf-archive"
+FILES_${PN}-tests = "${exec_prefix}/libexec/perf-core/tests"
+FILES_${PN}-python = "${exec_prefix}/libexec/perf-core/scripts/python"
+FILES_${PN}-perl = "${exec_prefix}/libexec/perf-core/scripts/perl"

Can we use ${libexecdir} here please rather than hardcode it?

I checked environment, the variable libexecdir is "/usr/lib/perf". If I use this variable, package can't be split successfully.

Best Regards
Chong

Quoted 8 lines

Cheers,

Richard

#5 lore raw
Quoted 41 lines · Chong Lu
Quoted 40 lines · Chong Lu
Quoted 37 lines · Richard Purdie
Quoted 21 lines · Chong Lu

Currently, perf can't split to perf-archive, perf-tests, perf-python and
perf-perl. All files are included in perf package. Change the files paths to
make split successfully and add PACKAGECONFIG to make main pkg depends on sub
pkgs as default.

---
  meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
  1 file changed, 12 insertions(+), 5 deletions(-)
meta/recipes-kernel/perf/perf.bb +0 -0
index bfd210c..baf0077 100644
@@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
    PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
  +PACKAGECONFIG ??= "archive perl python tests"

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 160

Quoted 10 lines
meta/recipes-kernel/perf/perf.bb +6 -0
+PACKAGECONFIG[archive] = ",,, ${PN}-archive"
+PACKAGECONFIG[perl] = ",,, ${PN}-perl"
+PACKAGECONFIG[python] = ",,, ${PN}-python"
+PACKAGECONFIG[tests] = ",,, ${PN}-tests"
+
  RDEPENDS_${PN} += "elfutils"
  RDEPENDS_${PN}-archive =+ "bash"
  RDEPENDS_${PN}-python =+ "bash python"
  RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
+RDEPENDS_${PN}-tests =+ "python"

I now realise the trick you're playing with PACKAGECONFIG here. Instead can we just define a package (say ${PN}-all but I'll accept a better name) which has dependencies on archive perl python tests so then the user can choose ${PN}, ${PN}-all or some other combination depending on their needs?

Quoted 5 lines
Quoted 1 line

OK, I will put archive perl python and tests in ${PN}-full.

Sorry, I don't think we should use a pkg include four sub pkgs. We have perf_feature_enabled to control whether enable perl and python, so it is hard to use feature if we put four sub pkgs in one pkg.

This isn't what I meant. I meant add a ${PN}-full package which RDEPENDS_${PN}-full = "${PN}-archive ${PN}-python ${PN}-perl ${PN}-tests"

Cheers,

Richard

author
#6 lore raw
Quoted 40 lines · Richard Purdie
Quoted 39 lines · Chong Lu
Quoted 38 lines · Chong Lu
Quoted 37 lines · Richard Purdie
Quoted 21 lines · Chong Lu

Currently, perf can't split to perf-archive, perf-tests, perf-python and
perf-perl. All files are included in perf package. Change the files paths to
make split successfully and add PACKAGECONFIG to make main pkg depends on sub
pkgs as default.

---
   meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
   1 file changed, 12 insertions(+), 5 deletions(-)
meta/recipes-kernel/perf/perf.bb +0 -0
index bfd210c..baf0077 100644
@@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
     PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
   +PACKAGECONFIG ??= "archive perl python tests"

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 160

Quoted 10 lines
meta/recipes-kernel/perf/perf.bb +6 -0
+PACKAGECONFIG[archive] = ",,, ${PN}-archive"
+PACKAGECONFIG[perl] = ",,, ${PN}-perl"
+PACKAGECONFIG[python] = ",,, ${PN}-python"
+PACKAGECONFIG[tests] = ",,, ${PN}-tests"
+
   RDEPENDS_${PN} += "elfutils"
   RDEPENDS_${PN}-archive =+ "bash"
   RDEPENDS_${PN}-python =+ "bash python"
   RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
+RDEPENDS_${PN}-tests =+ "python"

I now realise the trick you're playing with PACKAGECONFIG here. Instead can we just define a package (say ${PN}-all but I'll accept a better name) which has dependencies on archive perl python tests so then the user can choose ${PN}, ${PN}-all or some other combination depending on their needs?

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

OK, I will put archive perl python and tests in ${PN}-full.

Sorry, I don't think we should use a pkg include four sub pkgs. We have perf_feature_enabled to control whether enable perl and python, so it is hard to use feature if we put four sub pkgs in one pkg.

This isn't what I meant. I meant add a ${PN}-full package which RDEPENDS_${PN}-full = "${PN}-archive ${PN}-python ${PN}-perl ${PN}-tests"

Do you mean I should use:

PACKAGECONFIG ??= "full"
PACKAGECONFIG[full] = ",,, ${PN}-full"
RDEPENDS_${PN}-full = "${PN}-archive ${PN}-python ${PN}-perl ${PN}-tests"

Best Regards
Chong

Quoted 8 lines

Cheers,

Richard

#7 lore raw
Quoted 49 lines · Chong Lu
Quoted 40 lines · Richard Purdie
Quoted 39 lines · Chong Lu
Quoted 38 lines · Chong Lu
Quoted 37 lines · Richard Purdie
Quoted 21 lines · Chong Lu

Currently, perf can't split to perf-archive, perf-tests, perf-python and
perf-perl. All files are included in perf package. Change the files paths to
make split successfully and add PACKAGECONFIG to make main pkg depends on sub
pkgs as default.

---
   meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
   1 file changed, 12 insertions(+), 5 deletions(-)
meta/recipes-kernel/perf/perf.bb +0 -0
index bfd210c..baf0077 100644
@@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
     PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
   +PACKAGECONFIG ??= "archive perl python tests"

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 160

Quoted 10 lines
meta/recipes-kernel/perf/perf.bb +6 -0
+PACKAGECONFIG[archive] = ",,, ${PN}-archive"
+PACKAGECONFIG[perl] = ",,, ${PN}-perl"
+PACKAGECONFIG[python] = ",,, ${PN}-python"
+PACKAGECONFIG[tests] = ",,, ${PN}-tests"
+
   RDEPENDS_${PN} += "elfutils"
   RDEPENDS_${PN}-archive =+ "bash"
   RDEPENDS_${PN}-python =+ "bash python"
   RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
+RDEPENDS_${PN}-tests =+ "python"

I now realise the trick you're playing with PACKAGECONFIG here. Instead can we just define a package (say ${PN}-all but I'll accept a better name) which has dependencies on archive perl python tests so then the user can choose ${PN}, ${PN}-all or some other combination depending on their needs?

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

OK, I will put archive perl python and tests in ${PN}-full.

Sorry, I don't think we should use a pkg include four sub pkgs. We have perf_feature_enabled to control whether enable perl and python, so it is hard to use feature if we put four sub pkgs in one pkg.

This isn't what I meant. I meant add a ${PN}-full package which RDEPENDS_${PN}-full = "${PN}-archive ${PN}-python ${PN}-perl ${PN}-tests"

Quoted 5 lines

Do you mean I should use:

PACKAGECONFIG ??= "full"
PACKAGECONFIG[full] = ",,, ${PN}-full"
RDEPENDS_${PN}-full = "${PN}-archive ${PN}-python ${PN}-perl ${PN}-tests"

No, I do not believe we need a PACKAGECONFIG for this. Just install the particular package which fits your needs.

Cheers,

Richard

#8 lore raw
In reply to Chong Lu
Quoted 56 lines · Chong Lu
Quoted 19 lines · Richard Purdie
Quoted 18 lines · Chong Lu

Currently, perf can't split to perf-archive, perf-tests, perf-python and perf-perl. All files are included in perf package. Change the files paths to make split successfully and add PACKAGECONFIG to make main pkg depends on sub pkgs as default.

---
  meta/recipes-kernel/perf/perf.bb | 17 ++++++++++++-----
  1 file changed, 12 insertions(+), 5 deletions(-)
meta/recipes-kernel/perf/perf.bb +0 -0
index bfd210c..baf0077 100644
@@ -149,20 +149,27 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
 
  PACKAGES =+ "${PN}-archive ${PN}-tests ${PN}-perl ${PN}-python"
 
Quoted 16 lines

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 162

Quoted 11 lines
meta/recipes-kernel/perf/perf.bb +7 -0
+PACKAGECONFIG ??= "archive perl python tests"
+PACKAGECONFIG[archive] = ",,, ${PN}-archive"
+PACKAGECONFIG[perl] = ",,, ${PN}-perl"
+PACKAGECONFIG[python] = ",,, ${PN}-python"
+PACKAGECONFIG[tests] = ",,, ${PN}-tests"
+
  RDEPENDS_${PN} += "elfutils"
  RDEPENDS_${PN}-archive =+ "bash"
  RDEPENDS_${PN}-python =+ "bash python"
  RDEPENDS_${PN}-perl =+ "bash perl perl-modules"
+RDEPENDS_${PN}-tests =+ "python"

I now realise the trick you're playing with PACKAGECONFIG here. Instead can we just define a package (say ${PN}-all but I'll accept a better name) which has dependencies on archive perl python tests so then the user can choose ${PN}, ${PN}-all or some other combination depending on their needs?

OK, I will put archive perl python and tests in ${PN}-full.

Quoted 4 lines
Quoted 4 lines
meta/recipes-kernel/perf/perf.bb +0 -0
  RSUGGESTS_SCRIPTING = "${@perf_feature_enabled('perf-scripting', '${PN}-perl ${PN}-python', '',d)}"
  RSUGGESTS_${PN} += "${PN}-archive ${PN}-tests ${RSUGGESTS_SCRIPTING}"
 
Quoted 12 lines

meta/recipes-kernel/perf/perf.bb PACKAGE_ARCH = "${MACHINE_ARCH}" · line 172

Quoted 11 lines
meta/recipes-kernel/perf/perf.bb +5 -5
-FILES_${PN} += "${libexecdir}/perf-core ${exec_prefix}/libexec/perf-core ${libdir}/traceevent"
+FILES_${PN} += "${libdir}/traceevent"
  FILES_${PN}-dbg += "${libdir}/python*/site-packages/.debug"
-FILES_${PN}-archive = "${libdir}/perf/perf-core/perf-archive"
-FILES_${PN}-tests = "${libdir}/perf/perf-core/tests"
-FILES_${PN}-python = "${libdir}/python*/site-packages ${libdir}/perf/perf-core/scripts/python"
-FILES_${PN}-perl = "${libdir}/perf/perf-core/scripts/perl"
+FILES_${PN}-archive = "${exec_prefix}/libexec/perf-core/perf-archive"
+FILES_${PN}-tests = "${exec_prefix}/libexec/perf-core/tests"
+FILES_${PN}-python = "${exec_prefix}/libexec/perf-core/scripts/python"
+FILES_${PN}-perl = "${exec_prefix}/libexec/perf-core/scripts/perl"

Can we use ${libexecdir} here please rather than hardcode it?

Quoted 2 lines

I checked environment, the variable libexecdir is "/usr/lib/perf". If I use this variable, package can't be split successfully.

Perf should be putting the files into ${libexecdir}. We therefore probably need to set perfexecdir correctly, then use ${libexecdir} in FILES above.

Cheers,

Richard