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
Which versions does this apply to?
Can you please be more precise which files were outside their location, instead of posting autogenerated text? lensfun-0.2.5-r1 installs its USE=-doc files to /usr/share/doc/${P}, well that shouldn't make any problem, as long as the build system doesn't know anything about gentoo specific revisions - Betelgeuse just informed me about this policy. Erm, yeah, just tried lensfun-0.2.5-r1 with econf instead of ./configure but i got (as proclaimed in the ebuild) >>> Configuring source in /var/tmp/portage/media-libs/lensfun-0.2.5-r2/work/lensfun-0.2.5 ... ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --vectorization= Unknown command-line option: 'build=x86_64-pc-linux-gnu' Anyway, you have only mentioned ways to set the prefix /usr/share/doc, which is correct. But there is no way to tell a configure script to use a special suffix. I don't think that it's not worthwile hacking every package that doesn't use dodoc/dohtml to add the Gentoo revision to the /usr/share/doc/ directory entry.
It's not ${P} it's ${PF}; check the bug summary.
Fixed by trivial addition of --docdir=
