| Summary: | dev-db/framerd: documentation installed outside /usr/share/doc/${PF} | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
+ 03 Jan 2009; Christoph Mende <angelos@gentoo.org> + +files/framerd-2.4.3-asneeded.patch, framerd-2.4.3-r1.ebuild: + QA: Install documentation to /usr/share/doc/ (buf 241266), respect CC (bug + 243766), fix compilation with --as-needed (bug 247006) |
./usr/share/doc/framerd/ ./usr/share/doc/framerd/c-manual.html ./usr/share/doc/framerd/concepts.html ./usr/share/doc/framerd/fdscript-guide.html ./usr/share/doc/framerd/framerd-capi.html ./usr/share/doc/framerd/index.html ./usr/share/doc/framerd/r4rs.html ./usr/share/doc/framerd/r4rs_toc.html ./usr/share/doc/framerd/servers.html ./usr/share/doc/framerd/users-guide.html ./usr/share/doc/framerd/why.html ./usr/share/doc/framerd/www-guide.html ./usr/share/doc/framerd/framerd.css ./usr/share/doc/framerd/fdlogo.png dev-db/framerd-2.4.3-r1.tbz2 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