> we should at least test the unit tests against the installed version
I am not sure how to do that. Currently the unit tests use the libtraceevent.a generated at build time. So I suppose it should not really make any difference to run it in autopkgtest or at build time (see my patch in comment #5).
I thought about copying utest/Makefile in debian/tests/, replacing LIBTRACEEVENT_STATIC with the path to the installed libtraceevent.so and call "make test; ./trace-utest" in debian/tests/control.
I also thought about calling `./test-event -f /sys/kernel/tracing/events/ftrace/print/format` once the sample is built.
But I do not know if any of these methods would be "hacky" or good enough.
By the way there is the same issue on libtracefs so I guess finding a method fitting both packages could be easier to maintain.
> we should at least test the unit tests against the installed version
I am not sure how to do that. Currently the unit tests use the libtraceevent.a generated at build time. So I suppose it should not really make any difference to run it in autopkgtest or at build time (see my patch in comment #5).
I thought about copying utest/Makefile in debian/tests/, replacing LIBTRACEEVENT_ STATIC with the path to the installed libtraceevent.so and call "make test; ./trace-utest" in debian/ tests/control.
I also thought about calling `./test-event -f /sys/kernel/ tracing/ events/ ftrace/ print/format` once the sample is built.
But I do not know if any of these methods would be "hacky" or good enough.
By the way there is the same issue on libtracefs so I guess finding a method fitting both packages could be easier to maintain.