The bpftrace build tries to install two kinds of man pages: - existing man pages in troff format, which the ebuild installs correctly - the man page for bpftrace in asciidoc format, which the build tries to process via asciidoctor The latter is currently skipped when asciidoctor is not found. Since the ebuild does not depend on asciidoctor, this leads to a missing man page when asciidoctor is not yet installed on the build host. Unfortunately asciidoctor implies a pretty large dependency on ruby, which may not be great on development/debugging systems. Using asciidoc (the original python processor) does not work as it cannot process the input correctly, due to format changes. Luckily bpftrace publishes a man page archive as part of their release process, which means we can easily use the preprocessed bpftrace(8) page without having to pull in asciidoctor.
While bpftrace has helpful output via its -h option, the man page is much more detailed and really should be installed.
As it turns out the man page is _never_ installed for some reason, even when asciidoctor exists. This makes the fix even more important. :)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eda1b56db5cde357633e7db66045c6d337971663 commit eda1b56db5cde357633e7db66045c6d337971663 Author: Holger Hoffstätte <holger@applied-asynchrony.com> AuthorDate: 2024-08-15 09:00:43 +0000 Commit: Yixun Lan <dlan@gentoo.org> CommitDate: 2024-08-16 02:51:14 +0000 dev-debug/bpftrace: properly install bpftrace man page Closes: https://bugs.gentoo.org/937966 Closes: https://github.com/gentoo/gentoo/pull/38160 Signed-off-by: Holger Hoffstätte <holger@applied-asynchrony.com> Signed-off-by: Yixun Lan <dlan@gentoo.org> dev-debug/bpftrace/Manifest | 1 + .../bpftrace/{bpftrace-0.21.2.ebuild => bpftrace-0.21.2-r1.ebuild} | 3 +++ 2 files changed, 4 insertions(+)
