From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E40F7C4360C for ; Tue, 8 Oct 2019 15:37:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B9A6E2070B for ; Tue, 8 Oct 2019 15:37:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726138AbfJHPhO (ORCPT ); Tue, 8 Oct 2019 11:37:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45462 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725939AbfJHPhO (ORCPT ); Tue, 8 Oct 2019 11:37:14 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E09F63082E72; Tue, 8 Oct 2019 15:37:13 +0000 (UTC) Received: from localhost (ovpn-204-214.brq.redhat.com [10.40.204.214]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9BDE419C69; Tue, 8 Oct 2019 15:37:11 +0000 (UTC) Date: Tue, 8 Oct 2019 17:37:09 +0200 From: Jiri Benc To: Yonghong Song Cc: Jakub Kicinski , Andrii Nakryiko , David Ahern , Andrii Nakryiko , bpf , Networking , "Alexei Starovoitov" , Daniel Borkmann , Kernel Team Subject: Re: [PATCH v3 bpf-next 5/7] libbpf: move bpf_{helpers,endian,tracing}.h into libbpf Message-ID: <20191008173709.07da56ef@redhat.com> In-Reply-To: <62b1bc6b-8c8a-b766-6bfc-2fb16017d591@fb.com> References: <20191003212856.1222735-1-andriin@fb.com> <20191003212856.1222735-6-andriin@fb.com> <4fcbe7bf-201a-727a-a6f1-2088aea82a33@gmail.com> <20191004113026.4c23cd41@cakuba.hsd1.ca.comcast.net> <62b1bc6b-8c8a-b766-6bfc-2fb16017d591@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Tue, 08 Oct 2019 15:37:14 +0000 (UTC) Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On Fri, 4 Oct 2019 18:37:44 +0000, Yonghong Song wrote: > distro can package bpf/btf uapi headers into libbpf package. > Users linking with libbpf.a/libbpf.so can use bpf/btf.h with include > path pointing to libbpf dev package include directory. > Could this work? I don't think it would. Distros have often a policy against bundling files that are available from one package (in this case, kernel-headers or similar) in a different package (libbpf). The correct way is making the libbpf package depend on a particular version of kernel-headers (or newer). As I said, I don't see a problem here. It's not a special situation, it's just usual dependencies. Jiri