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
Seems to be fixed in 0.2.2, ssuominen@unique ~ $ qlist pyifp /usr/share/doc/pyifp-0.2.2/PKG-INFO.bz2 /usr/share/doc/pyifp-0.2.2/README.txt.bz2 /usr/bin/pyifp-test /usr/bin/backup-ifp /usr/lib64/python2.6/site-packages/_usb_core.so /usr/lib64/python2.6/site-packages/pyifp-0.2.2-py2.6.egg-info /usr/lib64/python2.6/site-packages/usb_core.py /usr/lib64/python2.6/site-packages/_ifp_core.so /usr/lib64/python2.6/site-packages/ifp.py /usr/lib64/python2.6/site-packages/ifp_core.py
Likely because it's an -r0 :P 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.
