Help files for dia-0.95.1 are ending up in /usr/share/doc/dia where dia's Help/Contents can't find them even with USE="gnome" It seems that the eautoreconf in the ebuild is creating a configure with additions over the original including: datarootdir='${prefix}/share' docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' I just modified: G2CONF="${G2CONF} $(use_enable gnome) $(use_with python) --docdir=\$(datadir)/gnome/help/\$(docname)/\$(lang)" but obviously gnome specific (Bug 147713), although maybe without yelp they aren't that useful anyway (Bug 135817). I only noticed this after emerging dia for this first time in months. Don't know if this is to do with autoconf-2.60 (dia used 2.59) - that has changed since I last successfully emerged dia. Portage 2.1.2_rc4-r1 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r4, 2.6.18-gentoo-r6 x86_64) ================================================================= System uname: 2.6.18-gentoo-r6 x86_64 Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz Gentoo Base System version 1.12.6 Last Sync: Thu, 28 Dec 2006 14:50:01 +0000 ccache version 2.3 [enabled] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10-r1 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="-march=nocona -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache collision-protect distlocks metadata-transfer parallel-fetch sandbox sfperms strict" LC_ALL="en_GB.UTF8" LINGUAS="en_GB en" MAKEOPTS="-j3"
Just to confirm this is a result of autoconf-2.6.
actually, I've tried to fix it in 0.96 ebuild but it appears that the documentation generation is just broken anyway because yelp complains about invalid XML. I'm adding upstream link to gnome-doc-utils migration bug because it's probably the most sensible thing to do (ie. wait for that).
*** Bug 135817 has been marked as a duplicate of this bug. ***
fixed in 0.96.1-r1
