Hello! Is there a plan to submit this to Factory? It is necessary to have it (and libtracefs) for building KernelShark 2, which I am planning to package and submit to Factory ASAP.

I'd be up with helping to maintain the package in Factory, if that helps.

Tony Jones (jones_tony) - about 3 years ago

I'd forgotten I'd submitted it before and it was rejected as perf was still providing the same files. I just pushed libtraceevent again plus a perf change

---

Dario Faggioli (dfaggioli) - about 3 years ago

maintainer

Great, and thanks! So, basically, for packaging the next version of KernelShark (and, I believe, of trace-cmd too) we need both libtraceevent and libtracefs. In fact, I have an SR to update it to latest upstream too, and was then planning to submit it to factory as well.

@jones_tony question: I see that we have this in the spec file:

%files -n %{soname}-plugins %dir %{_libdir}/%{sodname} %dir %{_libdir}/%{sodname}/plugins %{_libdir}/%{sodname}/plugins/*.so

This means we put plugins in /usr/lib64/traceevent1/plugins (because we use %{sodname}, which is %{dname}+%{sonum}).

Shouldn't they go in /usr/lib64/libtraceevent/plugins, i.e., shouldn't we just use %dname there?