From: Jiri Olsa <jolsa@redhat.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Andrey Ignatov <rdna@fb.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Song Liu <songliubraving@fb.com>,
bpf@vger.kernel.org
Subject: libbpf packaging
Date: Mon, 25 Mar 2019 13:21:34 +0100 [thread overview]
Message-ID: <20190325122134.GA14042@krava> (raw)
hi guys,
we want to package libbpf and I'd like to coordinate
with you on some issues I've met on this:
1) I think libbpf should be part of kernel-tools-libs and kernel-tools-libs-devel,
which would look like below (from early rpm build):
$ rpm -qpl kernel-tools-libs-5.0.0-1.fc31.x86_64.rpm
/usr/lib/.build-id
/usr/lib/.build-id/ca
/usr/lib/.build-id/ca/654da1e5ea553f985e28b8d98ad24e51f19e88
/usr/lib/.build-id/f6
/usr/lib/.build-id/f6/a788b316f26fbe70db47bfc0ef500348117023
/usr/lib64/libbpf.so.0
/usr/lib64/libbpf.so.0.0.1
/usr/lib64/libcpupower.so.0
/usr/lib64/libcpupower.so.0.0.1
/usr/share/licenses/kernel-tools-libs
/usr/share/licenses/kernel-tools-libs/COPYING
$ rpm -qpl kernel-tools-libs-devel-5.0.0-1.fc31.x86_64.rpm
/usr/include/bpf/bpf.h
/usr/include/bpf/btf.h
/usr/include/bpf/libbpf.h
/usr/include/cpufreq.h
/usr/include/cpuidle.h
/usr/lib64/libbpf.a
/usr/lib64/libbpf.so
/usr/lib64/libcpupower.so
Do you see libbpf as a standalone package or kernel-tools-libs* wuold be ok for you?
2) There's already bcc-devel's libbpf library packaged:
$ rpm -qf /usr/lib64/libbpf.so
bcc-devel-0.8.0-1.fc28.x86_64
so there's a conflict.. any chance we could rename libbpf to
something else like:
libbpf2.so
libbpfobject.so
libbpfbest.so
...?
I checked and I think those 2 conflicting libraries don't make
a valid case for using 'alternatives'.
Also the libbpf.so from bcc-devel has been there for some time
so we can't just remove/rename it.. ;-)
thoughts?
thanks,
jirka
next reply other threads:[~2019-03-25 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 12:21 Jiri Olsa [this message]
2019-03-25 12:52 ` libbpf packaging Daniel Borkmann
2019-03-25 16:03 ` Alexei Starovoitov
2019-03-25 17:19 ` Jiri Olsa
2019-03-25 17:21 ` Michal Rostecki
2019-03-25 19:34 ` Yonghong Song
2019-03-25 20:20 ` Jiri Olsa
2019-03-27 5:30 ` Yonghong Song
2019-03-27 7:20 ` Jiri Olsa
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=20190325122134.GA14042@krava \
--to=jolsa@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=rdna@fb.com \
--cc=songliubraving@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.