Bug#950760: RFS: libbpf/0.0.6-1 -- eBPF helper library (development files)
I just noticed that your packaging repo is currently empty.
Would you be able to push your current progress to Github
so that it's easier to review the source package?
On Thu, Feb 6, 2020 at 2:34 PM Sudip Mukherjee
<sudipm.mukherjee@gmail.com> wrote:
> So, do we also use epoch or shall I try the way which Paul suggested
> to add epoch only to the binary package?
My vote is to use libbpf's new versioning scheme and epoch 1 for both
source and binary packages. The primary benefit is simplicity:
IMO it's easier to reason about things that way.
It looks like upstream is trying to separate their own release
schedule from the kernel's. There is now a possibility that some
future libbpf release may contain changes not present in the
upstream kernel tree at all.
In this scenario, it would *only* make sense to use libbpf versioning
for the source package, so we might as well get both epoch adjustments
out of the way right now instead of raising this question again in the future.
Christian
Reply to: