In the post install action, the Pango ebuild generates an index of all modules in /etc/pango/pango.modules. The problem is, it does not consider the case where an alternate ROOT environment variable is set (e.g. when bootstrapping a custom distribution in a dedicated ROOT direcotry). In x11-libs/pango/pango-1.29.4.ebuild, the postinst method is as follows: pkg_postinst() { einfo "Generating modules listing..." local PANGO_CONFDIR="${EROOT}/etc/pango" multilib_enabled && PANGO_CONFDIR+="/${CHOST}" mkdir -p "${PANGO_CONFDIR}" pango-querymodules \ "${EROOT}"usr/$(get_libdir)/pango/1.6.0/modules/*.so \ > "${PANGO_CONFDIR}"/pango.modules } I'd suggest changing the module generation part to something like this: if [ "$ROOT" != "" ]; then mkdir -p "$ROOT"${PANGO_CONFDIR} chroot "$ROOT" /usr/bin/pango-querymodules > "$ROOT"${PANGO_CONFDIR}/pango.modules fi
Please give the exact error messages that you are seeing. It is not clear from your report what error you are experiencing.
The error message is, that the pango modules file (and the /etc/pango directory) does of course not exist on the target system when using a program which depends on pango, because it was not created by the ebuild. An example would be rrdtool graph, which throws the following error: (process:24917): Pango-CRITICAL **: No modules found: No builtin or dynamically loaded modules were found. PangoFc will not work correctly. This probably means there was an error in the creation of: '/etc/pango/pango.modules' You should create this file by running: pango-querymodules > '/etc/pango/pango.modules' (process:24917): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common' (process:24917): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin'
We will need to add a "|| die" to pango-querymodules too :S
+ 01 Apr 2012; Pacho Ramos <pacho@gentoo.org> pango-1.29.4.ebuild, + pango-1.30.0.ebuild: + Add a die statement to catch pango.modules generation problems like bug + #409741 by Nicolas Perrenoud. + Now we need you to re-emerge it after syncing to get the failure and post it here
