Currently, the bcc package puts all the python tools that are included in the /tools directory of the upstream bcc git repo into /usr/share/bcc/tools however, this makes them difficult to find. As such its not immediately obvious that they are even installed. I'm recommending that the default should be to place them in the system path or at least make it optional through a use-flag. Looking at other package systems I can see that at least Ubuntu makes the tools available on the path by placing them in /usr/sbin: https://github.com/iovisor/bcc/blob/master/INSTALL.md#ubuntu---binary While the main bcc package is first and foremost important, most casual users will mostly be using the package for the tools that it comes with. As such, I think that its a good idea to place them prominently on the system rather than the user having to hunt them down in /usr/share Reproducible: Always Steps to Reproduce: N/A
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4befc9afad985df29fcce013b05cd0e1748539b1 commit 4befc9afad985df29fcce013b05cd0e1748539b1 Author: Patrick McLean <chutzpah@gentoo.org> AuthorDate: 2021-12-02 07:20:34 +0000 Commit: Patrick McLean <chutzpah@gentoo.org> CommitDate: 2021-12-02 07:20:45 +0000 dev-util/bcc: revbump, symlink tools to system path (bug #741466) This is much easier with eapi-dosym.eclass, so let's finally get around to adding this to the ebuild. Closes: https://bugs.gentoo.org/741466 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Patrick McLean <chutzpah@gentoo.org> dev-util/bcc/{bcc-0.23.0.ebuild => bcc-0.23.0-r1.ebuild} | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
