--- Comment #5 from Iñaki Ucar <i.ucar86(a)gmail.com> ---
(In reply to Jiri Olsa from comment #3)
however, upstream team decided to keep and maintain GitHub libbpf
sources (which are regirarly sync from kernel tree) to maintain
compatibility in between distributions and mainly to have stable
relases of libbpf based on github tree tags rather then on random
kernel versions (from libbpf point of view)
But that GitHub mirror follows bpf-next, right? So the question is whether it
could happen that an update of the standalone libbpf has a soname bump that
makes it incompatible with the kernel versions packaged in Fedora (which cannot
happen if libbpf is a subpackage of kernel-tools, because it has the same
versioning and provides from the same "snapshot").
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component