libcap-ng: use update-alternatives for libcap-ng.so
PATCH 1/1 libcap-ng: use update-alternatives for libcap-ng.so
open-iscsi-user also uses the doc 'libcap-ng.so'.
open-iscsi-user has a priority of 60.
--- meta/recipes-support/libcap-ng/libcap-ng_0.8.2.bb | 6 ++++++ 1 file changed, 6 insertions(+)
meta/recipes-support/libcap-ng/libcap-ng_0.8.2.bb +6 -0
@@ -6,6 +6,12 @@ EXTRA_OECONF += "--without-python --without-python3" BBCLASSEXTEND = "native nativesdk" +inherit update-alternatives + +ALTERNATIVE_PRIORITY = "100" +ALTERNATIVE_${PN}-dev = "libcap-ng.so" +ALTERNATIVE_LINK_NAME[libcap-ng.so] = "${libdir}/libcap-ng.so" + do_install_append() { # Moving libcap-ng to base_libdir if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then
Signature · 1 line
2.25.1
Quoted 1 line · wangmy
open-iscsi-user also uses the doc 'libcap-ng.so'.
A "doc"? If it is in libdir this is a dev symlink? Is it an alternate provider of this library or is this some kind of linking intercept functionality? It seems like a bad idea...
meta/recipes-support/libcap-ng/libcap-ng_0.8.2.bb EXTRA_OECONF += "--without-python --without-python3" · line 13
Quoted 6 lines
meta/recipes-support/libcap-ng/libcap-ng_0.8.2.bb +5
-0+inherit update-alternatives + +ALTERNATIVE_PRIORITY = "100" +ALTERNATIVE_${PN}-dev = "libcap-ng.so" +ALTERNATIVE_LINK_NAME[libcap-ng.so] = "${libdir}/libcap-ng.so"
Cheers,
Richard
The bb file content of open-iscsi-user in meta-virtual is incorrect, resulting in a conflict. Libcap-ng does not need to be modified. Please ignore this patch
--
Best Regards
---------------------------------------------------
Wang Mingyu
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu Road, Nanjing, 210012, China
TEL: +86+25-86630566-8568
COINS: 79988548
FAX: +86+25-83317685
MAIL: [email protected]
http://www.fujitsu.com/cn/fnst/
Quoted 26 lines
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Richard Purdie
Sent: Wednesday, July 21, 2021 5:36 PM
To: Wang, Mingyu/王 鸣瑜 <[email protected]>; [email protected]
Subject: Re: [OE-core] [PATCH] libcap-ng: use update-alternatives for libcap-ng.soQuoted 1 line · wangmy
open-iscsi-user also uses the doc 'libcap-ng.so'.
A "doc"? If it is in libdir this is a dev symlink? Is it an alternate provider of this library or is this some kind of linking intercept functionality? It seems like a bad idea...
meta/recipes-support/libcap-ng/libcap-ng_0.8.2.bb EXTRA_OECONF += "--without-python --without-python3" · line 13
Quoted 6 lines
meta/recipes-support/libcap-ng/libcap-ng_0.8.2.bb +5
-0+inherit update-alternatives + +ALTERNATIVE_PRIORITY = "100" +ALTERNATIVE_${PN}-dev = "libcap-ng.so" +ALTERNATIVE_LINK_NAME[libcap-ng.so] = "${libdir}/libcap-ng.so"Cheers,
Richard