Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #64764

Re: libbpf distro packaging

Show all headers | View raw

On 8/13/19 2:24 PM, Jiri Olsa wrote:
> On Mon, Aug 12, 2019 at 07:04:12PM +0000, Julia Kartseva wrote:
>> I would like to bring up libbpf publishing discussion started at [1].
>> The present state of things is that libbpf is built from kernel tree, e.g. [2]
>> For Debian and [3] for Fedora whereas the better way would be having a
>> package built from github mirror. The advantages of the latter:
>> - Consistent, ABI matching versioning across distros
>> - The mirror has integration tests
>> - No need in kernel tree to build a package
>> - Changes can be merged directly to github w/o waiting them to be merged
>> through bpf-next -> net-next -> main
>> There is a PR introducing a libbpf.spec which can be used as a starting point: [4]
>> Any comments regarding the spec itself can be posted there.
>> In the future it may be used as a source of truth.
>> Please consider switching libbpf packaging to the github mirror instead
>> of the kernel tree.
>> Thanks
>>
>> [1] https://lists.iovisor.org/g/iovisor-dev/message/1521
>> [2] https://packages.debian.org/sid/libbpf4.19
>> [3] http://rpmfind.net/linux/RPM/fedora/devel/rawhide/x86_64/l/libbpf-5.3.0-0.rc2.git0.1.fc31.x86_64.html
>> [4] https://github.com/libbpf/libbpf/pull/64
> 
> hi,
> Fedora has libbpf as kernel-tools subpackage, so I think
> we'd need to create new package and deprecate the current
> 
> but I like the ABI stability by using github .. how's actually
> the sync (in both directions) with kernel sources going on?

The upstream kernel's tools/lib/bpf/ is always source of truth. Meaning, changes need
to make it upstream first and they are later synced into the GH stand-alone repo.

Thanks,
Daniel

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-08-13 14:50 +0200
  Re: libbpf distro packaging Daniel Borkmann <daniel@iogearbox.net> - 2019-08-13 17:00 +0200
    Re: libbpf distro packaging Andrii Nakryiko <andrii.nakryiko@gmail.com> - 2019-08-13 20:50 +0200
  Re: libbpf distro packaging Andrii Nakryiko <andrii.nakryiko@gmail.com> - 2019-08-13 20:50 +0200
    Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-08-21 23:30 +0200
      Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-08-23 11:40 +0200
        Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-08-26 09:10 +0200
          Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-08-28 09:40 +0200
            Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-09-30 13:40 +0200
              Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-10-03 13:30 +0200
                Re: libbpf distro packaging Andrii Nakryiko <andrii.nakryiko@gmail.com> - 2019-10-03 18:50 +0200
                Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-10-03 19:50 +0200
              Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-10-08 10:00 +0200
                Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-10-16 12:20 +0200
                Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2019-12-20 15:50 +0100
                Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2020-03-05 16:10 +0100
                Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2020-03-10 16:20 +0100
                Re: libbpf distro packaging Jiri Olsa <jolsa@redhat.com> - 2020-03-10 19:10 +0100

csiph-web