Summary: | x11-misc/driconf-0.9.1 imports gtk python module during src_compile and src_install | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | Unclassified | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Mokrejš
2009-01-31 22:50:26 UTC
(In reply to comment #0) > /usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could > not open display > warnings.warn(str(e), _gtk.Warning) This has nothing to do with portage. It's the ebuild or build system doing that. This is a side effect of intentional upstream behaviour, please see line 58 in setup.py - it tries to confirm Python bindings for GTK+2 are available by importing them. In principle we could patch this section of the setup out, the ebuild already ensures the presence of pygtk - but do we really want to bother? It would be nice to decide one way or another and finally close this bug, though. |