[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190826064235.GA17554@krava>
Date: Mon, 26 Aug 2019 08:42:35 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Alexei Starovoitov <ast@...com>
Cc: Julia Kartseva <hex@...com>,
Andrii Nakryiko <andrii.nakryiko@...il.com>,
"labbott@...hat.com" <labbott@...hat.com>,
"acme@...nel.org" <acme@...nel.org>,
"debian-kernel@...ts.debian.org" <debian-kernel@...ts.debian.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Andrey Ignatov <rdna@...com>, Yonghong Song <yhs@...com>,
"jolsa@...nel.org" <jolsa@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>
Subject: Re: libbpf distro packaging
On Fri, Aug 23, 2019 at 04:00:01PM +0000, Alexei Starovoitov wrote:
> On 8/23/19 2:22 AM, Jiri Olsa wrote:
> > btw, the libbpf GH repo tag v0.0.4 has 0.0.3 version set in Makefile:
> >
> > VERSION = 0
> > PATCHLEVEL = 0
> > EXTRAVERSION = 3
> >
> > current code takes version from libbpf.map so it's fine,
> > but would be great to start from 0.0.5 so we don't need to
> > bother with rpm patches.. is 0.0.5 planned soon?
>
> Technically we can bump it at any time.
> The goal was to bump it only when new kernel is released
> to capture a collection of new APIs in a given 0.0.X release.
> So that libbpf versions are synchronized with kernel versions
> in some what loose way.
> In this case we can make an exception and bump it now.
I see, I dont think it's worth of the exception now,
the patch is simple or we'll start with 0.0.3
jirka
Powered by blists - more mailing lists