> Specific binary packages built, but NOT to be promoted to main: python3-bpfcc,
> bpfcc-tools, [...]
I would have thought that getting these tools would have been the entire point of this MIR. There's an immense amount of value built in them, and without the tools we've got the framework but no pre-built way to consume it. These pre-built tools are 99% of why I want this package promoted.
(A similar question was raised for the bpftrace package -- we might as well just stop reviewing these packages if we remove the actual tools from the packages.)
> Specific binary packages built, but NOT to be promoted to main: python3-bpfcc,
> bpfcc-tools, [...]
I would have thought that getting these tools would have been the entire point of this MIR. There's an immense amount of value built in them, and without the tools we've got the framework but no pre-built way to consume it. These pre-built tools are 99% of why I want this package promoted.
(A similar question was raised for the bpftrace package -- we might as well just stop reviewing these packages if we remove the actual tools from the packages.)
What's the rationale for not promoting the tools?
Thanks