You're getting this bug because the package in summary installs its documentation (or at least part of it) outside the usual /usr/share/doc/${PF} directory. First, please keep in mind that this bug might not be noticeable for -r0 ebuilds, but it might be for -r1 and later, since if the ebuild has same name and version of the package, for -r0 it might correspond properly. To fix this, if the package uses autotools, recent version (autoconf 2.61+) have two ./configure switches: --docdir and --htmldir to decide where to put the documentation. Older versions might require you override docdir/htmldir or other custom variables during make install. For non-autotooled build systems, good luck, since I cannot tell you how to achieve the proper results, the same holds true with totally broken buildsystems even when based on autotools. Thanks, Diego
There is a line in a Makefile.am, which overrides the docdir option: --- gjiten-2.6-r1-orig/help/ja/Makefile.am Tue Mar 02 13:32:05 2010 +0100 +++ gjiten-2.6-r1/help/ja/Makefile.am Tue Mar 02 13:33:57 2010 +0100 @@ -1,4 +1,3 @@ -docdir = $(datadir)/doc/gjiten doc_DATA = gjiten-doc.ja.html EXTRA_DIST = $(doc_DATA) Additionally the following fixes in the ebuild seem necessary: diff /usr/portage/app-dicts/gjiten/gjiten-2.6-r1.ebuild gjiten-2.6-r1.ebuild 32,33d31 < # bug #294891 < epatch "${FILESDIR}"/${P}-docdir.patch 38,39d35 < # bug #294891 < G2CONF="${G2CONF} --docdir=/usr/share/doc/${PF}"
Created attachment 221883 [details, diff] proposed patch
Created attachment 221885 [details] proposed new ebuild
gjiten-2.6-r3 solves this