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
I'm not sure it's worth efforts in this case so suggestions are welcome. nip2 uses two pathes in sources: #define NIP_DOCPATH "$VIPSHOME" G_DIR_SEPARATOR_S "share" G_DIR_SEPARATOR_S \ "doc" G_DIR_SEPARATOR_S PACKAGE G_DIR_SEPARATOR_S "html" #define VIPS_DOCPATH "$VIPSHOME" G_DIR_SEPARATOR_S "share" G_DIR_SEPARATOR_S \ "doc" G_DIR_SEPARATOR_S "vips" G_DIR_SEPARATOR_S "html" Fixed nip2 path is an easy task, but it's impossible to fix vips path as we'll have either to rebuild nip2 every time vips is bumped or we'll end with broken paths and unopenable documentation. In other words, fixing nip2 path is half of solution while fixing both paths will introduce nontrivial dependencies into packages. Is there any need to fix nip2 path only?
a bit of a hassle, but... symlink to vips ebuild to keep the path constant? something like `dosym /usr/share/doc/${PF}/html /usr/share/vips/html`?
vips fixed in 7.22.4.
And nip2 fixed in 7.22.3. Thank you for report. And thank you Samuli for suggestion. I've just kept installation of symlinks in both packages...
