| 1 |
bpfcc (0.31.0+ds-5) unstable; urgency=medium |
| 2 |
|
| 3 |
Starting with this version, all binary files for the libbpf-tools |
| 4 |
package have been renamed to $filename-libbpf suffix. |
| 5 |
. |
| 6 |
For example: execsnoop => execsnoop-libbpf |
| 7 |
. |
| 8 |
This is to ensure that we have consistency across the different |
| 9 |
variants of the tools, namely: bpfcc-tools, perf-tools-unstable and |
| 10 |
libbpf-tools |
| 11 |
|
| 12 |
-- Ritesh Raj Sarraf <[email protected]> Mon, 17 Mar 2025 15:06:03 +0530 |
| 13 |
|
| 14 |
bpfcc (0.2.0-2) unstable; urgency=medium |
| 15 |
|
| 16 |
Starting with version 0.2.0-2, all binary files have been renamed to |
| 17 |
$filename-bpfcc suffix. |
| 18 |
. |
| 19 |
For example: execsnoop => execsnoop-bpfcc |
| 20 |
. |
| 21 |
Similarly, the manpages have been renamed. This is done to accommodate |
| 22 |
users who would like to use perf-tools-unstable, parallelly with the |
| 23 |
eBPF Compiler Collection Tools from the bpfcc package. |
| 24 |
. |
| 25 |
Both upstreams work closely on the projects, thus the common names. |
| 26 |
|
| 27 |
-- Ritesh Raj Sarraf <[email protected]> Fri, 30 Dec 2016 23:42:55 +0530 |