summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core
diff options
context:
space:
mode:
authorRasmus Villemoes <rasmus.villemoes@prevas.dk>2020-07-06 10:17:39 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-07-08 10:37:12 +0100
commit59602324626e773f59544be0e7745fc461b6195c (patch)
treee9cb30ba0d2adab44e65a2373a0797e7210c1bf9 /meta/recipes-core
parent90e8954c0d4a715b6b24e1674b74dcab1315a835 (diff)
downloadpoky-59602324626e773f59544be0e7745fc461b6195c.tar.gz
coreutils: don't split stdbuf to own package with single-binary
Commit 992cec44 (coreutils: Move stdbuf into an own package coreutils-stdbuf) breaks package-qa when the single-binary PACKAGECONFIG is used: ERROR: coreutils-8.32-r0 do_package_qa: QA Issue: /usr/bin/stdbuf contained in package coreutils-stdbuf requires /usr/bin/coreutils, but no providers found in RDEPENDS_coreutils-stdbuf? [file-rdeps] ERROR: coreutils-8.32-r0 do_package_qa: QA run found fatal errors. Please consider fixing them. With that PACKAGECONFIG, /usr/bin/stdbuf is just a simple "script" containing the single line #!/usr/bin/coreutils --coreutils-prog-shebang=stdbuf Since there's no point splitting stdbuf to its own package when all the functionality is in the single big coreutils binary anyway, fix this by not creating the separate stdbuf package for the single-binary case. But also make sure that the coreutils-stdbuf item always exists so recipes can always RDEPEND on coreutils-stdbuf. (From OE-Core rev: 74d24b5b895198898944260136d05e991a203c11) Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core')
-rw-r--r--meta/recipes-core/coreutils/coreutils_8.32.bb15
1 files changed, 13 insertions, 2 deletions
diff --git a/meta/recipes-core/coreutils/coreutils_8.32.bb b/meta/recipes-core/coreutils/coreutils_8.32.bb
index 2422f8634e..f8ae3fd94c 100644
--- a/meta/recipes-core/coreutils/coreutils_8.32.bb
+++ b/meta/recipes-core/coreutils/coreutils_8.32.bb
@@ -59,9 +59,20 @@ base_bindir_progs = "cat chgrp chmod chown cp date dd echo false hostname kill l
59 59
60sbindir_progs= "chroot" 60sbindir_progs= "chroot"
61 61
62PACKAGE_BEFORE_PN_class-target += "coreutils-stdbuf" 62# Split stdbuf into its own package, so one can include
63# coreutils-stdbuf without getting the rest of coreutils, but make
64# coreutils itself pull in stdbuf, so IMAGE_INSTALL += "coreutils"
65# always provides all coreutils
66PACKAGE_BEFORE_PN_class-target += "${@bb.utils.contains('PACKAGECONFIG', 'single-binary', '', 'coreutils-stdbuf', d)}"
63FILES_coreutils-stdbuf = "${bindir}/stdbuf ${libdir}/coreutils/libstdbuf.so" 67FILES_coreutils-stdbuf = "${bindir}/stdbuf ${libdir}/coreutils/libstdbuf.so"
64RDEPENDS_coreutils_class-target += "coreutils-stdbuf" 68RDEPENDS_coreutils_class-target += "${@bb.utils.contains('PACKAGECONFIG', 'single-binary', '', 'coreutils-stdbuf', d)}"
69
70# However, when the single-binary PACKAGECONFIG is used, stdbuf
71# functionality is built into the single coreutils binary, so there's
72# no point splitting /usr/bin/stdbuf to its own package. Instead, add
73# an RPROVIDE so that rdepending on coreutils-stdbuf will work
74# regardless of whether single-binary is in effect.
75RPROVIDES_coreutils += "${@bb.utils.contains('PACKAGECONFIG', 'single-binary', 'coreutils-stdbuf', '', d)}"
65 76
66# Let aclocal use the relative path for the m4 file rather than the 77# Let aclocal use the relative path for the m4 file rather than the
67# absolute since coreutils has a lot of m4 files, otherwise there might 78# absolute since coreutils has a lot of m4 files, otherwise there might