5 May
2014
5 May
'14
12:56 a.m.
Sadly, the `perf trace` command has a dependency on libaudit for a few convenience functions. I'm curious about what people feel the best approach would be here... adding back audit to [community] is ugly since it's not going to work, but building it and statically linking it in the linux-tools package is overly complex. The lesser evil seems to be adding only a libaudit package... but it's still not going to work if someone tries to use it for what it's intended to do. I'll probably go with this if there's no saner idea.