From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/libcap: drop host-libcap dependency
Date: Sat, 8 Jan 2022 21:41:33 +0100 [thread overview]
Message-ID: <20220108203526.DA7AC83456@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=0651b22d638faecb3688f1fd4e0760c31bfba893
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
host-libcap was added as a dependency of libcap in commit
efae605c88deb15d9c50fd67bdd80f46a78b06c1 because back then at
installation time, the setcap utility was called.
However, since commit 57155c6b6a7a40523075626353375109fe159c04, we use
RAISE_SETFCAP=no, which disables calling setcap at install
time. Therefore, having host-libcap built before libcap is no longer
needed.
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
package/libcap/libcap.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/libcap/libcap.mk b/package/libcap/libcap.mk
index 42acca9082..1207995333 100644
--- a/package/libcap/libcap.mk
+++ b/package/libcap/libcap.mk
@@ -11,7 +11,7 @@ LIBCAP_LICENSE = GPL-2.0 or BSD-3-Clause
LIBCAP_LICENSE_FILES = License
LIBCAP_CPE_ID_VENDOR = libcap_project
-LIBCAP_DEPENDENCIES = host-libcap host-gperf
+LIBCAP_DEPENDENCIES = host-gperf
LIBCAP_INSTALL_STAGING = YES
HOST_LIBCAP_DEPENDENCIES = host-gperf
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2022-01-08 20:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220108203526.DA7AC83456@busybox.osuosl.org \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).