bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Yonghong Song <yhs@fb.com>
Cc: Michal Rostecki <mrostecki@opensuse.org>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrey Ignatov <rdna@fb.com>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Song Liu <songliubraving@fb.com>, bpf <bpf@vger.kernel.org>,
	Brenden Blanco <bblanco@gmail.com>
Subject: Re: libbpf packaging
Date: Mon, 25 Mar 2019 21:20:09 +0100	[thread overview]
Message-ID: <20190325202009.GA14511@krava> (raw)
In-Reply-To: <e13f6295-e7ae-80c4-67af-6e8551a375a1@fb.com>

On Mon, Mar 25, 2019 at 07:34:42PM +0000, Yonghong Song wrote:
> 
> 
> On 3/25/19 10:21 AM, Michal Rostecki wrote:
> > On Mon, Mar 25, 2019 at 09:03:11AM -0700, Alexei Starovoitov wrote:
> >>>> 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 don't think we should rename the official libbpf package, this will
> >>> just create plain confusion and will make it much harder for potential
> >>> users to adapt in the long-term since we aim for /everyone/ to consume
> >>> official libbpf library instead of hacking their own.
> >>>
> >>> I think bcc folks are migrating to official libbpf as well, at least
> >>> that was my impression. Imho, this would need fixing on bcc side then.
> >>
> >> bcc migrated to libbpf some time ago.
> > 
> > And the libbpf.so file which is installed with bcc is "our" libbpf. bcc
> > simply uses libbpf (from the auto-synced standalone repo[0]) as a
> > submodule[1]. To package libbpf and bcc properly in Linux distros we
> > need a possibility to use bcc with shared libbpf library - which
> > probably can be achiveved by small change in bcc's CMakeLists.txt.
> 
> I think we should rename bcc libbpf.so to a different name (maybe 
> libbcc_bpf.so) to avoid confusions between bcc libbpf and libbpf repo.
> The bcc libbpf.so is different from libbpf repo it contains some wrappers...

that'd be great first step.. then we could add libbpf
package and make bcc depend on it as suggested by Michal

> 
> I will propose to iovisor/bcc mailing list.

please keep me in cc for that

thanks,
jirka

> 
> > 
> > The standalone repo[0] might be a better base for creating a package
> > than full kernel sources. And using %soversion%+git%sha% (i.e.
> > 0.0.2+git33b017) might be a better version pattern of that package.
> > 
> > Cheers,
> > Michal
> > 
> > [0] https://github.com/libbpf/libbpf
> > [1] https://github.com/iovisor/bcc/blob/master/CMakeLists.txt#L12-L16
> > 

  reply	other threads:[~2019-03-25 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 12:21 libbpf packaging Jiri Olsa
2019-03-25 12:52 ` 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 [this message]
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=20190325202009.GA14511@krava \
    --to=jolsa@redhat.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=bblanco@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=mrostecki@opensuse.org \
    --cc=rdna@fb.com \
    --cc=songliubraving@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).