All available builds of pygtk seem to SLOT pygtk to 1.2 or 2 -- see below --
which means that the porthole 0.3.1 ebuild won't emerge properly, because it
looks for a pygtk that's slotted to 0. If you grep for a slot of 2 in the
ebuild file, it compiles and runs. I'm not uploading a patch because SLOTing
is still a bit of mystery to me and I don't want to upload something that might
break someone's system. Plus it's changing one letter.
BUILD ERROR:
remora pkg # emerge -v porthole
Calculating dependencies ...done!
>>> emerge (1 of 1) app-portage/porthole-0.3.1 to /
>>> md5 src_uri ;-) porthole-0.3.1.tar.bz2
* pygtk was not merged with the gnome
* USE flag. Porthole requires pygtk be
* built with this flag for libglade support.
!!! ERROR: app-portage/porthole-0.3.1 failed.
!!! Function pkg_setup, Line 35, Exitcode 0
!!! pygtk missing gnome support
remora pkg # grep SLOT /usr/portage/dev-python/pygtk/*.ebuild
/usr/portage/dev-python/pygtk/pygtk-0.6.11-r1.ebuild:SLOT="1.2"
/usr/portage/dev-python/pygtk/pygtk-0.6.11.ebuild:SLOT="1.2"
/usr/portage/dev-python/pygtk/pygtk-1.99.13-r1.ebuild:SLOT="2"
/usr/portage/dev-python/pygtk/pygtk-2.0.0-r1.ebuild:SLOT="2"
/usr/portage/dev-python/pygtk/pygtk-2.0.0.ebuild:SLOT="2"
/usr/portage/dev-python/pygtk/pygtk-2.2.0.ebuild:SLOT="2"
FROM:
/usr/portage/app-portage/porthole/porthole-0.3.1.ebuild
THIS: if grep 0 ${pygtk_install}/SLOT > /dev/null; then
SHOULD BE THIS: if grep 2 ${pygtk_install}/SLOT > /dev/null; then
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
