I emerged pixz and didn't get a man page. The project has a man page at https://github.com/vasi/pixz/blob/master/src/pixz.1.asciidoc app-text/asciidoc-9.0.5-r1::gentoo was installed. If I got the discussion in #gentoo right, the live version has a man page and there could be a dependency problem. Reproducible: Always
I looked into this for a while and the situation is very strange. My final determination was this: an additional dependency (app-text/asciidoc) is required just to generate a manpage, but one is provided pre-generated (named pixz.1) and is just not being installed. there's a substantial amount of the author's conditional logic in the package related to this "man handling" as is, but the end result is that all lines for manpages in the Makefile scripts get auto-commented out. This applies to pixz-1.0.7.ebuild: My simplest solution: in the .ebuild src_configure() section right before ending "econf" command: add: export man_MANS=pixz.1 This will cause the make install script to install this pre-generated "pixz.1" manpage file. (this variable came from the authors own automake "src/Makefile.am") The 9999 version from git does not have this problem, and this only applies to 1.0.7 release.
(CCing gyakovlev as he's interested in pixz iirc?)
(In reply to genBTC from comment #1) > This applies to pixz-1.0.7.ebuild: > My simplest solution: > in the .ebuild src_configure() section right before ending "econf" command: > add: > > export man_MANS=pixz.1 > Works for me: git diff pixz-1.0.7.ebuild pixz-1.0.7-r1.ebuild |cat diff --git a/pixz-1.0.7.ebuild b/pixz-1.0.7-r1.ebuild index cb614f5..f96c204 100644 --- a/pixz-1.0.7.ebuild +++ b/pixz-1.0.7-r1.ebuild @@ -43,6 +43,7 @@ src_configure() { # Workaround silly logic that breaks cross-compiles. # https://github.com/vasi/pixz/issues/67 export ac_cv_file_src_pixz_1=$([[ -f src/pixz.1 ]] && echo yes || echo no) + export man_MANS=pixz.1 econf }
Created attachment 764229 [details] modified ebuild with additional line for the man page
