I've been browsing around looking for a good GUI toolkit for Python (purely for tinkering), and anygui seems to have the most potential. It is obviously still an alpha (or pre-alpha) grade piece of software. However, I don't feel that it is entirely necessarily to go about masking it. I'm submitting a small patch (tiny, even). It fixes the problem mentioned in "package.mask" with GTK -- by disabling that backend. (Who needs GTK anyway? <grin>) Basically, remove "gtk" from _backends in __init__.py. The ebuild itself would benefit from some modifications to remove PyGTK dependencies. As for what's happening in general ... perhaps python needs to have one of the backend share libraries preloaded? Didn't look too closely....
Created attachment 5857 [details, diff] Tiny GTK Disabling Patch
i dont see no mentioning of PyGTK, only of PyQT. So QT should be disabled ? Now this is an relativly old report, so things might have changed... There doesnt seem to be too much activity in the anygui departement, is it worth putting time in for the Gentoo team you think or can it be removed from the tree (it has been in package.mask for ages).
The line in the ebuild DEPEND is: "gtk? ( dev-python/pygtk )" I poked around their site. The last CVS commits seem to have occurred about six weeks ago. They aren't making fast progress, but the project doesn't seem to be abandoned yet. Maybe more people would get interested if our anygui ebuild wasn't broken? <shrug> I don't know. I'll agree that this project/ebuild isn't very important at this point in time. I guess the question is: how much does it cost to keep the ebuild alive versus the risk that this project/ebuild will never reach a non-alpha state?
I hardly would call it our job to keep projects alive. Anyway that's not really my point here, why do you want gtk disabled when it seems to work fine, the qt bindings are said to be problematic in package.mask .
I have no problems with the Qt bindings, but do have problems with the GTK bindings. __init__.py wasn't working for me when it tried to bind to GTK. I don't have Qt installed.... Whatever. If both GTK and Qt are broken, then it should probably be toasted.
but it builds.. runtime problems aren't really an ebuild problem.
So, if mozilla compiled, but didn't start, then you would (with a straight-face) say that that would not be an ebuild problem?
it doesnt have to be no. Anyway i wouldnt compare some alpha wrapper toolkit with mozilla
it's all too unstable and p.masked anyway. imho anygui should be removed from portage. closing this one.
