Hi Jakub, Laura and Jiri Olsa (Cc others), Subj: iovisor-dev] minutes: IO Visor TSC/Dev Meeting (To: iovisor-dev <[email protected]>) On Wed, 31 Oct 2018 14:30:25 -0700 "Brenden Blanco" <[email protected]> wrote: > Jakub: > * working on getting libbpf packaged separately and released by distros > * FB has external mirror github.com/libbpf/libbpf >
I noticed from the iovisor-dev minutes that you have plans for packaging libbpf from the kernel tree. And via that I noticed the github repo https://github.com/libbpf/libbpf, created by Yonghong Song. I'm uncertain if it makes sense to maintain this library outside the kernel git tree?!? To be honest, I have very little knowledge about building RPMs and other packages formats. I just wanted to point out that RHEL and Fedora is now shipping bpftool, which also part of kernel git tree. (Now I need input from Jiri Olsa and Laura to correct below statements:) AFAIK bpftool RPM-package[1] is part of the "Source Package" kernel-tools, which AFAIK gets build directly from the distro kernel git tree via kernel.spec file. This also happens for perf RPM-package[2] see section "Source Package" also point to kernel-tools. So, my question is, can we ship/package libbpf in the same way? Notice, that an increasing number of tools are linking/using libbpf, e.g. perf, bpftool, Suricata, (selftests and samples/bpf). [1] https://fedora.pkgs.org/28/fedora-x86_64/bpftool-4.16.0-1.fc28.x86_64.rpm.html [2] https://fedora.pkgs.org/29/fedora-x86_64/perf-4.18.10-300.fc29.x86_64.rpm.html -- Best regards, Jesper Dangaard Brouer MSc.CS, Principal Kernel Engineer at Red Hat LinkedIn: http://www.linkedin.com/in/brouer -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1515): https://lists.iovisor.org/g/iovisor-dev/message/1515 Mute This Topic: https://lists.iovisor.org/mt/28036138/21656 Group Owner: [email protected] Unsubscribe: https://lists.iovisor.org/g/iovisor-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
