Bug#948041: impossible to update libbpf without updating the kernel
On Wed, Jan 15, 2020 at 12:50:16PM +0000, Sudip Mukherjee wrote:
> On Wed, Jan 15, 2020 at 06:12:05AM +0000, Jonathan Nieder wrote:
> > I agree --- if upstream development were happening in
> > https://github.com/libbpf/libbpf then this would be a no-brainer. It
> > appears to instead be a mirror of the source that's in the kernel
> > repo, though.
> That will be difficult as all of them are dependent on the ftrace hooks
> that are in the kernel.
What will be difficult?
> > > Why should we switch from kernel sources to GH is a frequently asked
> > > question so the reason was explained in libbpf README [1].
Let's go through it one by one.
"Consistent versioning across distributions."
Maybe, but the kernel is also versioned consistently.
"No ties to any specific kernel, transparent handling of older kernels."
What? Either they are upstream for it or patch the source. But this
point means it can't be a direct mirror. So what is it?
"Continuous integration testing via TravisCI."
"Static code analysis via LGTM and Coverity."
Both are not restricted to this repo.
> > If I'm reading that correctly, the intent appears to be that it would
> > allow faster libbpf upgrades.
> Yes, one of my intent. Faster and independent.
And how does it do that, without being upstream of the source?
Sorry, but I intend to end this discussion here.
Bastian
--
It would be illogical to assume that all conditions remain stable.
-- Spock, "The Enterprise Incident", stardate 5027.3
Reply to: