| Summary: | net-im/pebrot: documentation installed outside /usr/share/doc/${PF} | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | Gentoo Net-im project <net-im> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
*** Bug 319359 has been marked as a duplicate of this bug. *** I'm skeptical about what upstream considers docs, but it is what it is. I've fixed setup.py so that everything that was installed in /usr/share/doc/pebrot gets put into /usr/share/doc/${PF} and pebrot.py has been changed to look there for the logos.
|
./usr/share/doc/pebrot/ ./usr/share/doc/pebrot/README ./usr/share/doc/pebrot/pebrotrc ./usr/share/doc/pebrot/AUTHORS ./usr/share/doc/pebrot/ChangeLog ./usr/share/doc/pebrot/COPYING ./usr/share/doc/pebrot/utils/ ./usr/share/doc/pebrot/utils/getkeys.py ./usr/share/doc/pebrot/utils/enc.py ./usr/share/doc/pebrot/utils/keymap.py ./usr/share/doc/pebrot/utils/example.py ./usr/share/doc/pebrot/utils/transparent_bg/ ./usr/share/doc/pebrot/utils/transparent_bg/usedefault.c ./usr/share/doc/pebrot/utils/transparent_bg/readme ./usr/share/doc/pebrot/utils/transparent_bg/setup.py ./usr/share/doc/pebrot/logos/ ./usr/share/doc/pebrot/logos/moo.txt ./usr/share/doc/pebrot/logos/readme ./usr/share/doc/pebrot/logos/pebrot.txt net-im/pebrot-0.8.8.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