[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201103102351.13a2bb9a@hermes.local>
Date: Tue, 3 Nov 2020 10:23:51 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: David Ahern <dsahern@...il.com>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii.nakryiko@...il.com>,
Hangbin Liu <haliu@...hat.com>,
Alexei Starovoitov <ast@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
David Miller <davem@...emloft.net>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Networking <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
Jiri Benc <jbenc@...hat.com>,
Andrii Nakryiko <andrii@...nel.org>,
Toke Høiland-Jørgensen <toke@...hat.com>
Subject: Re: [PATCHv3 iproute2-next 0/5] iproute2: add libbpf support
On Tue, 3 Nov 2020 09:47:00 -0800
Alexei Starovoitov <alexei.starovoitov@...il.com> wrote:
> On Tue, Nov 3, 2020 at 9:36 AM David Ahern <dsahern@...il.com> wrote:
> >
> > On 11/3/20 1:46 AM, Daniel Borkmann wrote:
> > > I thought last time this discussion came up there was consensus that the
> > > submodule could be an explicit opt in for the configure script at least?
> >
> > I do not recall Stephen agreeing to that, and I certainly did not.
>
> Daniel,
>
> since David is deaf to technical arguments,
> how about we fork iproute2 and maintain it separately?
A submodule is not a practical viable option.
Please come back when you are ready to use distro libbpf packages.
This seems a microcosm of the Linux packaging problem that was discussed
around Kubernetes and "vendorizaton"
Powered by blists - more mailing lists