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 trying to fix this in 2.4.0, but how is this supposed to work? I'd really like an upgrade from fpc 2.4.0 to a potential future 2.4.0-r1 to not change the location of the docs, because changing the location of the docs means fpc-ide's configuration (which refers to those docs) becomes invalid and the help stops working.
I think you should drop the fpc-ide ebuild completely. As it seems to be build from the same sources as fpc anyway you could instead control by a USE flag in fpc if the ide should be build additionally. That way fpc and its ide stay always in sync and you have full control of the installed docs (which should go to /usr/share/doc/${PF}).
Should be fixed in fpc-2.4.4 in the tree. Also, fpc-ide is controlled via the ide USE flag as mentioned in comment #2.
