Skip to contentSkip to conversation

pkgconf: don't use alternatives

PATCH In review Ross Burton 2 participants 2 messages Sep 11, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 pkgconf: don't use alternatives

There's no need to do alternatives as pkgconf and pkg-config won't be installed at the same time, and pkg-config doesn't do alternatives either.

---
 meta/recipes-devtools/pkgconf/pkgconf_1.5.3.bb | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)
meta/recipes-devtools/pkgconf/pkgconf_1.5.3.bb +1 -3
index 2021d1ac602..415478d5cf9 100644
@@ -24,7 +24,7 @@ SRC_URI = "\
 SRC_URI[md5sum] = "c21743bca14c882c0f282746168a5edc"
 SRC_URI[sha256sum] = "d3468308553c94389dadfd10c4d1067269052b5364276a9d24a643c88485f715"
 
-inherit autotools update-alternatives
+inherit autotools
 
 EXTRA_OECONF += "--with-pkg-config-dir='${libdir}/pkgconfig:${datadir}/pkgconfig'"
 
@@ -46,8 +46,6 @@ do_install_append_class-native () {
     install -m755 ${B}/pkg-config-esdk ${D}${bindir}/pkg-config-esdk
 }
 
-ALTERNATIVE_${PN} = "pkg-config"
-
 # When using the RPM generated automatic package dependencies, some packages
 # will end up requiring 'pkgconfig(pkg-config)'.  Allow this behavior by
 # specifying an appropriate provide.
Signature · 1 line
2.11.0
#1 lore raw

✗ patchtest: failure for pkgconf: don't use alternatives

== Series Details ==

Series: pkgconf: don't use alternatives
Revision: 1
URL : https://patchwork.openembedded.org/series/14014/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at d638fe0cc8)

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe