From: Julia Kartseva <hex@fb.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Alexei Starovoitov <ast@fb.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
"labbott@redhat.com" <labbott@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"debian-kernel@lists.debian.org" <debian-kernel@lists.debian.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Andrey Ignatov <rdna@fb.com>, Yonghong Song <yhs@fb.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"md@linux.it" <md@linux.it>
Subject: Re: libbpf distro packaging
Date: Mon, 7 Oct 2019 00:25:51 +0000 [thread overview]
Message-ID: <040A8497-C388-4B65-9562-6DB95D72BE0F@fb.com> (raw)
In-Reply-To: <20190930111305.GE602@krava>
On 9/30/19, 4:13 AM, "Jiri Olsa" <jolsa@redhat.com> wrote:
> heya,
> FYI we got it through.. there's libbpf-0.0.3 available on fedora 30/31/32
> I'll update to 0.0.5 version as soon as there's the v0.0.5 tag available
>
> jirka
Hi Jiri,
I wonder what are the steps to make libbpf available for CentOS {7|8} as well?
One (likely the quickest) way to do that is to publish it to Fedora's EPEL [1].
I have a little concern about dependencies, namely elfutils-libelf-devel and
elfutils-devel are sourced directly by CentOS repos, e.g. [2], not sure if
dependencies from another repo are fine.
Thoughts? Thanks!
[1] https://fedoraproject.org/wiki/EPEL
[2] http://mirror.centos.org/centos/7/os/x86_64/Packages/
next prev parent reply other threads:[~2019-10-07 0:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 19:04 libbpf distro packaging Julia Kartseva
2019-08-13 12:24 ` Jiri Olsa
2019-08-13 14:11 ` Daniel Borkmann
2019-08-13 18:26 ` Andrii Nakryiko
2019-08-13 18:23 ` Andrii Nakryiko
[not found] ` <FA139BA4-59E5-43C7-8E72-C7B2FC1C449E@fb.com>
2019-08-20 22:27 ` Julia Kartseva
2019-08-21 21:09 ` Jiri Olsa
2019-08-23 9:22 ` Jiri Olsa
2019-08-23 16:00 ` Alexei Starovoitov
2019-08-26 6:42 ` Jiri Olsa
2019-08-27 22:30 ` Julia Kartseva
2019-08-28 7:12 ` Jiri Olsa
2019-09-30 11:13 ` Jiri Olsa
2019-09-30 18:18 ` Julia Kartseva
2019-10-03 0:50 ` Julia Kartseva
2019-10-03 11:10 ` Jiri Olsa
2019-10-03 16:24 ` Andrii Nakryiko
2019-10-03 17:29 ` Jiri Olsa
2019-10-07 0:25 ` Julia Kartseva [this message]
2019-10-08 7:39 ` Jiri Olsa
2019-10-11 21:14 ` Julia Kartseva
2019-10-16 10:01 ` Jiri Olsa
2019-12-19 21:37 ` Julia Kartseva
2019-12-20 13:58 ` Jiri Olsa
2020-03-05 0:22 ` Julia Kartseva
2020-03-05 14:18 ` Jiri Olsa
2020-03-10 14:57 ` Jiri Olsa
2020-03-10 17:18 ` Julia Kartseva
2020-03-10 17:49 ` 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=040A8497-C388-4B65-9562-6DB95D72BE0F@fb.com \
--to=hex@fb.com \
--cc=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=debian-kernel@lists.debian.org \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=labbott@redhat.com \
--cc=md@linux.it \
--cc=netdev@vger.kernel.org \
--cc=rdna@fb.com \
--cc=yhs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).