First of all, read this thread that I opened about the problem: http://forums.gentoo.org/viewtopic-t-716176.html It explains the problem better than I would do here (and I can avoid to rewrite it here). IN SHORT: Since about yesterday =app-misc/gramps-3.0.3 requires >=dev-python/gnome-python-desktop-2.6 as a dependency, which pulls in other 34 new packages!!! An alternative dependency is dev-python/libgnome-python, but all versions (2.22.1, 2.22.3) are in the ~testing branch as of now: it requires only 5 packages. I installed GRAMPS some time ago and used it with no problems, with the (+stable) =dev-python/gnome-python-2.22.0 as dependency. It's been replaced by libgnome-python in RDEPEND because gnome-python has been split, but 2.22.0 wasn't split yet, so it's been a bad idea since there aren't any +stable libgnome-python versions. The result is that if I want to use GRAMPS with =dev-python/gnome-python-2.22.0 I can't, even if it would work!! MY SOLUTION: Change RDEPEND with: || ( dev-python/libgnome-python >=dev-python/gnome-python-2.22.0 >=dev-python/gnome-python-desktop-2.6 ) * uses dev-python/libgnome-python: it will be used when it'll be in the +stable branch or if added in package.keywords * if point 1 isn't satisfied, uses >=dev-python/gnome-python-2.22.0: 2.22.0 isn't split yet and is enough to let it compile and run; >=2.22.1 are split (so it also emerges dev-python/libgnome-python) * as last resort, uses >=dev-python/gnome-python-desktop-2.6, which pulls in lots of dependencies for a non-GNOME user Moreover, in the GRAMPS FAQs http://gramps-project.org/wiki/index.php?title=FAQ you can find this: "GRAMPS is a GTK application. GRAMPS needs to have the pygtk libraries installed on the system. As long as these libraries are installed, GRAMPS should function. It will operate under the GNOME desktop, KDE desktop, or any other desktop. If the GNOME bindings for Python are installed on the system, GRAMPS will have additional functionality. The GRAMPS project recommends version 2.8 or higher of GTK." So GNOME bindings should be optional (maybe with the USE flag "gnome"), not strictly required!!! And that would be great since I don't use GNOME and I don't want useless packages emerged in my system. Let me know what you think. Thanks. Reproducible: Always Steps to Reproduce:
I changed the depenencies according to your suggestion. Gramps does check in any case for the Gnome bindings when running configure, so the user needs it installed. I will have to think about a solution in the next week. Thanks for your report.
Good, it now behaves as it should ;)
(In reply to comment #2) > Good, it now behaves as it should ;) The hard-coded gnome2-python test is removed in trunk, so I think we can introduce USE=gnome for gramps 3.0.4
(In reply to comment #3) > (In reply to comment #2) > > Good, it now behaves as it should ;) > > The hard-coded gnome2-python test is removed in trunk, so I think we can > introduce USE=gnome for gramps 3.0.4 3.0.4 with USE=gnome in the tree. Please test.
My USE="reports -debug -gnome" I successfully compiled with dev-python/gnome-python installed (I need it for another package). Anyway, I tried to unmerge dev-python/gnome-python and then emerge gramps but it stops on configure: checking for python platform... linux2 checking for python script directory... ${prefix}/lib64/python2.5/site-packages checking for python extension module directory... ${exec_prefix}/lib64/python2.5/site-packages checking for sh... /bin/sh checking Python bindings for gtk2.10 (pygtk2>=2.10.0)... 2.14.2 checking Python bindings for gnome... configure: error: **** The python bindings for gnome2 (gnome2-python) could not be found.
(In reply to comment #5) > My USE="reports -debug -gnome" Sorry, but I did not read properly...the fix is going into 3.1 not, 3.0.4. Will remove the USE flag and tell you when it is really ready.
(In reply to comment #6) > Sorry, but I did not read properly...the fix is going into 3.1 not, 3.0.4. > Will remove the USE flag and tell you when it is really ready. Ok: let's wait for 3.1 ;)
3.1.0 is there, please test.
Successfully compiled with USE="reports -debug -gnome -spell" and dev-python/gnome-python and dev-python/libgnome-python NOT installed. I think the problem is now really fixed ;)