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
We install Qt documentation in /usr/share/doc/qt-${PV}/ I see no need to change this.
*** Bug 295101 has been marked as a duplicate of this bug. ***
QA policy states that quite clearly.
qt-core, qt-assistant and qt-demo install documentation files to /usr/share/doc/qt-${PV}/ as that is the docdir location defined in the qt4-build.eclass. In my opinion this is the most logical location. qt-core[doc] will install html documentation for all of Qt into that directory, and qt-assistant installs binary "compressed help" files there, again covering all of Qt. The fact that the canonical location that QA demands isn't used, is because we use split ebuilds, which facilitates recompiling individual modules, instead of all of Qt, e.g. in case of a revbump of one of the modules with an added patch. So we ask QA to consider this a valid exception from the rule. Alternatively, we could move the documentation to /usr/share/qt4/doc/ if that is somehow considered a better location.
Works for me. Thank you for the explanation.
