libtraceevent
libtraceevent
- Devel package for openSUSE:Factory
-
4
derived packages
- Links to openSUSE:Factory / libtraceevent
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:libraries:c_c++/libtraceevent && cd $_
- Create Badge
Refresh
Refresh
Source Files (show unmerged sources)
Filename | Size | Changed |
---|---|---|
libtraceevent-1.7.3.tar.gz | 0000152363 149 KB | |
libtraceevent-rpmlintrc | 0000000096 96 Bytes | |
libtraceevent.changes | 0000005829 5.69 KB | |
libtraceevent.spec | 0000003216 3.14 KB |
Latest Revision
buildservice-autocommit
accepted
request 1094115
from
Dario Faggioli (dfaggioli)
(revision 28)
baserev update by copy to link target
Comments 4
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.
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
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?