Updated ebuild for gramps version 2.0.0
Created attachment 59602 [details] gramps-2.0.0.ebuild
Created attachment 60136 [details] gramps-2.0.1.ebuild Adds required version of software. >=dev-lang/python-2.3 >=dev-python/pygtk-2.4 >=dev-python/gnome-python-2.6 >=gnome-base/gnome-vfs-2.8
The lastest stable version of gramps is now 2.0.2-1. I have been running this version since it was 1.1.95 and have not had any problems with it. The portage tree needs to be updated to include gramps version 2.x as this is a much improved version of the program. I am running on an AMD64 machine so this should also at the very least be marked as ~amd64.
*** Bug 92345 has been marked as a duplicate of this bug. ***
this application is now up to version 2.0.3. can we please get these added?
Version 2.0.5 was released a month ago. I'll start working on an ebuild, but shouldn't this be added to portage soon? It's been 2.5 months since the 2.0.0 ebuild was provided, yet nothing has happened...
Created attachment 65313 [details] Gramps 2.0.5 ebuild
Comment on attachment 65313 [details] Gramps 2.0.5 ebuild Emerges fine, and as far as I have been able to tell, also runs withour problems.
I tried the 2.0.5 ebuild and I get this error on running: Traceback (most recent call last): File "/usr/share/gramps/gramps.py", line 81, in ? import gramps_main File "/usr/share/gramps/gramps_main.py", line 56, in ? import GrampsBSDDB File "/usr/share/gramps/GrampsBSDDB.py", line 36, in ? from bsddb import dbshelve, db ImportError: No module named bsddb
This is just a guess on my part, but have you emerged Python without the berkdb USE flag? This should of course be checked for in the ebuild, so if this is the solution, I'll update it when I get back from work.
Adding berkdb to the python USE flags did the trick.
Created attachment 65459 [details] Updated ebuild gramps-2.0.5 Updated it to test for the berkdb USE flag in python.
*** Bug 102681 has been marked as a duplicate of this bug. ***
Just a question: Would it be possible to make Gramps use less dependencies? I had to install over 40 packages before I was able to use it.
Created attachment 66120 [details] gramps-2.0.6.ebuild This is for the 2.0.6 release. It differs from the 2.0.5 ebuild because it downgrades the requirement for pygtk to version 2.4.
Created attachment 66121 [details] gnome-python-2.6.1-r1.ebuild The main culprit in the dependancy help for non-gnome users of gramps appears to be gnome-python. This ebuild adds some use flags so that you can turn off some of the things that gramps does not need from gnome-python. Try: ACCEPT_KEYWORDS="~x86" USE="nonautilus nobonobo nognomeprint" emerge -pv =gnome-python-2.6.1-r1 This ebuild is untested. I am not about to remove gnome from my system to see if it works :-)
Richard, thanks for the gnome-python-2.6.1-r1 ebuild. I installed it and was able to "depclean" the following packages: gnome-base/libgnomeprint selected: 2.10.3 protected: none omitted: none net-print/libgnomecups selected: 0.2.0 protected: none omitted: none gnome-base/libgnomeprintui selected: 2.10.2 protected: none omitted: none However, libbonobo is still installed. To understand the whole situation, I removed gramps and all it's dependencies and reemerged the whole thing. Here ist the output: emerge -av --tree gramps These are the packages that I would merge, in reverse order: Calculating dependencies ...done! [ebuild N ] app-misc/gramps-2.0.6 -debug 0 kB [1] [ebuild N ] dev-python/reportlab-1.18 0 kB [ebuild N ] dev-python/imaging-1.1.4-r1 -X -tcltk 406 kB [ebuild N ] dev-python/pyxml-0.8.3-r1 712 kB [ebuild N ] dev-lang/swig-1.3.21 -X -guile -java -perl -php -python -ruby -tcltk 1,975 kB [ebuild N ] dev-python/gnome-python-2.6.1-r1 -debug -gtkhtml +nobonobo +nognomeprint +nonautilus 0 kB [1] [ebuild N ] x11-libs/libzvt-2.0.1-r2 -debug 0 kB [ebuild N ] dev-python/pyorbit-2.0.1 -debug 237 kB [ebuild N ] gnome-base/gnome-panel-2.10.2 -debug -doc -eds -static 0 kB [ebuild N ] gnome-base/gnome-menus-2.10.1 -debug 0 kB [ebuild N ] x11-libs/libwnck-2.10.0 -debug -doc 0 kB [ebuild N ] gnome-base/gnome-desktop-2.10.1 -debug 0 kB [ebuild N ] app-text/scrollkeeper-0.3.14 -nls 663 kB [ebuild N ] app-text/docbook-xml-dtd-4.1.2-r5 73 kB [ebuild N ] app-text/docbook-sgml-utils-0.6.14 -tetex 122 kB [ebuild N ] app-text/docbook-xml-dtd-4.3 81 kB [ebuild N ] app-text/docbook-xsl-stylesheets-1.68.1-r1 944 kB [ebuild N ] app-text/build-docbook-catalog-1.2 3 kB [ebuild N ] www-client/links-2.1_pre17-r1 -X -directfb -fbcon -gpm -javascript -jpeg -livecd -png -ssl -svga -tiff -unicode 3,743 kB [ebuild N ] app-text/docbook-xml-simple-dtd-1.0-r1 30 kB [ebuild N ] app-text/docbook-xml-simple-dtd-4.1.2.4-r2 34 kB [ebuild N ] app-text/docbook-sgml-dtd-3.1-r3 54 kB [ebuild N ] app-text/docbook-sgml-dtd-3.0-r3 42 kB [ebuild N ] app-text/docbook-dsssl-stylesheets-1.79 271 kB [ebuild N ] dev-perl/SGMLSpm-1.03-r5 91 kB [ebuild N ] app-text/docbook-sgml-dtd-4.0-r3 54 kB [ebuild N ] app-text/docbook-sgml-dtd-4.1-r3 55 kB [ebuild N ] app-text/openjade-1.3.2-r1 873 kB [ebuild N ] app-text/opensp-1.5.1 -nls 1,385 kB [ebuild N ] app-text/sgml-common-0.6.3-r4 74 kB [ebuild N ] x11-themes/gnome-themes-2.10.1 -accessibility -debug 2,497 kB [ebuild N ] x11-themes/gtk-engines-2.6.3-r1 -debug 458 kB [ebuild N ] x11-themes/gnome-icon-theme-2.10.1 -debug 2,918 kB [ebuild N ] x11-themes/hicolor-icon-theme-0.5 30 kB [ebuild N ] gnome-base/libgnomeui-2.10.0 -debug -doc -jpeg 1,613 kB [ebuild N ] gnome-base/gnome-keyring-0.4.2 -debug 360 kB [ebuild N ] gnome-base/libbonoboui-2.8.1 -debug -doc 997 kB [ebuild N ] gnome-base/libgnome-2.10.0 -debug -doc 850 kB [ebuild N ] media-sound/esound-0.2.34 -alsa -ipv6 -tcpd 310 kB [ebuild N ] gnome-base/libgnomecanvas-2.10.0 -X -debug -doc 562 kB [ebuild N ] gnome-base/libglade-2.5.1 -debug -doc 310 kB [ebuild N ] gnome-base/gnome-vfs-2.10.1-r1 -debug -doc -gnutls -hal -howl -ipv6 -samba -ssl 1,860 kB [ebuild N ] gnome-base/libbonobo-2.8.1 -debug -doc 1,036 kB [ebuild N ] gnome-base/gnome-mime-data-2.4.2 -debug 829 kB [ebuild N ] gnome-base/gconf-2.10.0 -debug -doc 1,693 kB [ebuild N ] gnome-base/orbit-2.12.2 -debug -doc -ssl 662 kB Total size of downloads: 28,927 kB As you can see, it still wants to install libbonobo. BTW: I removed all USE flags, except "nobonobo", "nognomeprint" and "nonautilus".
The problem is that gnome-vfs has a dependency on gnome-base/libbonobo. I don't know enough about gnome-vfs to know whether this could be made optional. May be one of the gnome herd might be listen?
IMHO the gnome guys should try to make the gnome ebuilds more configurable by USE flags. That would help a lot :-)
The README for gramps-2.0.5 also says pygtk 2.4 or greater, but the website claims 2.5.0 or greater should be used, so I went for that.I don't know if it makes any noticeable difference.
re comment #20. The 2.0.8 autoconf says "checking Python bindings for gtk2.4 (pygtk2>=2.3.4)" So, this should be used as the minimun dependent version. Can this please go into the tree? Depcleaning would be nice but can be done afterwards, the latest portage verions of gramps is currently 1.1 or so.
(In reply to comment #21) > Can this please go into the tree? Depcleaning would be nice but can be done > afterwards, the latest portage verions of gramps is currently 1.1 or so. That would definately be a good thing to put a current version of gramps into portage. Can anybody tell me why this is not done until now?
Created attachment 69644 [details] Gramps 2.0.8 ebuild Updated ebuild. This version of gramps definitely works well. I vote for its introduction into the portage tree.
I installed OK from this ebuild, but when trying to run get: darren@garbo ~ $ gramps (gramps.py:24780): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Fatal Python error: could not import ORBit module Aborted I've re-emerged two slotted versions of gnome-base/orbit to no effect.
tsk. Needed to re-emerge pyorbit (Python bindings for ORBit). Now it works.
The original post here is 6 months old... Isn't it about time something gets committed? The latest version of gramps in portage is 1.0.11... I realize this might not be the most popular package in portage, but come on...
Created attachment 74558 [details] ebuild for version 2.0.9 Just a version bump to 2.0.9. Is this ever going to be merged?
we had this problem previously too (forget the bug number now) where most people were maintaining PORTDIR_OVERLAY versions of the gramps ebuild. Then one of the gnome herd said he'd look after it but that looks like it's fallen by the wayside. I'd suggest using an overlay for it agian. I think the gentoo gnome people have bigger fish to fry, especially since gnome 2.12 was released in September and it's still not marked stable :(
Okay, imported into portage under ~arch. Please do the usual number in ~2 hours.
