Gramps - User contributions [en]

Mac OS X:Build from source

2008-04-10T19:58:28Z

Tkott:

[[Category:Developers/Packaging]]
There are three different ways of installing Gramps on Mac OS X. The linked pages provide step by step instructions.

=== Fink ===

Installing Gramps as an X11 application is achieved by downloading and installing the packages on which Gramps depends using software called fink. The process is a bit longwinded, but most of the features of Gramps work, and drag and drop and mouse clicks work very well. If you choose this route, you may be able to get some help both from the Gramps community and the fink community. Detailed instructions can be found here: [[Mac OS X fink]].

Unfortunately, due to [http://wiki.finkproject.org/index.php/Fink:Packaging:The_Great_Gnome_Update The Great Gnome Update], fink does not currently support any version of gramps beyond about 2.2.6. As of January 2008, the estimated date for release of an update that would support later versions of gramps is 'soon'.

Note that fink is designed to support binary distributions and automatic building of packages, but the latest version of gramps that is 'fully' supported by fink is about version 1 of gramps (i.e. '''very''' old), so after you have installed the dependencies, you have to install gramps 'manually'.

=== MacPorts ===

MacPorts is essentially a similar type of program to fink.

See [[Mac OS X MacPorts]] on the installation process.

=== Native Mac OS X ===

You can install it as a [[native Mac OS X]] application which means that Gramps windows have the normal appearance of Macintosh Windows. This choice has fewer dependencies on installing other components. However, it has the disadvantage that drag and drop does not work, and there are issues with mouse clicks going missing, which make it much more difficult to enter information like sources which apply to many different people in your family tree. This is also in some ways a less mainstream approach so it may be harder to find help if you get into difficulties.

=== Questions ===

==== Am I ready for X11? ====

Installing with either fink or MacPorts is simpler that installing as a native application, but the Gramps windows have an X11 appearance. To see whether you can get use dto this appearance, you could download and install [http://www.openoffice.org/ OpenOffice] which is very easy to do and will show you what an X11 application looks like. Installing OpenOffice will not be wasted, because you will need it to be able to open reports from Gramps.

Another option is to download [http://www.neooffice.org/ NeoOffice], which is a port of OpenOffice using Java so that it looks like a native Mac OS X application.

==== Are there any other options? ====

(1) Virtual Server

Yet another option is to install a virtual server on your Mac (like VMware Fusion), create a virtual machine running Linux, and install Gramps in there. A Gnome based distro like Ubuntu would be a good choice for the Linux system.

(2) After already having all the dependencies installed

If you have all of the dependent libraries installed already, this should be straightforward. Just download the .tar.gz file, unpack it, and follow the INSTALL instructions.

==== Is this going to be too complicated for me? ====

The process is not very straightforward, and there will almost certainly be problems like unresolved dependencies, files not found on the various servers, download of files just stalls indefinitely and questions asked by scripts to which you don't know the answer. Nevertheless, installation is possible and I think gramps is worth the trouble. I suggest you have a look at the instructions for [http://www.captnswing.net/2004/02/12/nicotine.html|Installing SoulSeek] - this is a similar process, but actually ''SoulSeek'' is easier because it is fully integrated into the fink process. This might give you some idea of the requirements for perseverance. If you don't think you could install ''SoulSeek'' then you certainly won't be able to install Gramps. '''The converse is not true'''

User talk:AndreStadler

2008-04-08T14:15:43Z

Tkott: New page: Hi, I would be glad to help out if I can. Could you just let me know what problems you are running into? For example, did your installation fail at a particular point in the instructions l...

Hi, I would be glad to help out if I can. Could you just let me know what problems you are running into? For example, did your installation fail at a particular point in the instructions listed here: [[Mac_OS_X_MacPorts]]? The more information the better!

Tomek [[User:tkott]]

Mac OS X:Build from source:fink

2007-06-15T04:58:34Z

Tkott: instructions to fix PDFLib.py error

== Introduction ==

This page describes how to install Gramps on OSX using X11. The process uses fink or a similar program called macports to install the packages that gramps depends on. Gramps does work, although there are some glitches which are described below.

The author of the fink guide thanks the original author from which that part of the guide was written, and for the help of people on the Gramps list for helping them work through the stumbling blocks!

The fink guide applies to Mac OS X 10.4.8, and Gramps 2.2.6, but might work with other versions.

The macports guide applied to Mac OS X 10.4.8 and Gramps 2.2.6, but should work otherwise.

=== General Caveats ===

* As stated above, these instructions were for installing 2.2.6 on Mac OS X 10.4.8, but should work more widely.
* Production of a guide like this should really only be done after repeating the installation from a clean machine, and repeating again till the guide exactly matches the actual process - doing so would take a lot of time; the authors have each only done the installation once, so your experience will almost certainly differ from theirs.
* The process is not very straightforward, and there will almost certainly be problems like unresolved dependencies, files not found on the various servers, download of files just stalls indefinitely and questions asked by scripts to which you don't know the answer. Nevertheless, installation is possible and I think gramps is worth the trouble. I suggest you have a look at the instructions for [http://www.captnswing.net/2004/02/12/nicotine.html|Installing SoulSeek] - this is a similar process, but actually ''SoulSeek'' is easier because it is fully integrated into the fink process. This might give you some idea of the requirements for perseverance. If you don't think you could install ''SoulSeek'' then you certainly won't be able to install Gramps. '''The converse is not true'''

== Installing Gramps on Mac OS X via fink to use X11 ==

* You are installing from the 'unstable' fink tree, so the versions of the packages you install may vary from day to day, and there could be problems with them.

=== Installation instructions ===

==== Install X11 ====

If you have not already installed X11, install it from the Apple OS X installation disks.

====Install Developer Tools====

If you have not already installed the Developer Tools, install them from a recent Apple OS X installation disks (there may be a CD labelled XCode Tools, or an XCode folder on the install DVD). If your installation disk is not very recent, it may be better to download the tools from the [http://developer.apple.com/tools/xcode/ Apple web-site] (free registration required to access the development tools) because some of the build process will not work with an old version of the tools.

====Install and update fink====

This was much more difficult than it should have been. From reading some of the fink mailing lists, I think there may have been some problems with updates to the fink mirrors at the time.

<ol><li> Download the appropriate version of [http://fink.sourceforge.net/download/index.php?phpLang=en fink]. These instructions were tried with fink 0.8.1. You may need the [http://fink.sourceforge.net/doc/users-guide/ Fink User's Guide].
<li> Install fink by opening the disk image and double clicking on the installer.pkg.
<li> You could use FinkCommander to provide a GUI to fink, but it is not worth the trouble, because I wasn't sure that it actually offered all the packages that I wanted, and sometimes did not allow me to type in responses to questions (this is presumably a bug). I suggest you use Terminal. In Terminal type <tt>'''fink self-update'''</tt> This should download package descriptions and update core packages including fink itself. I thought it would be best to do this update before switching from source to binary distribution, but I had to try the whole updating process several times before I actually managed to get it to succeed, so this may be a bad choice.
<li> In Terminal type <tt>'''fink configure'''</tt> This should run the fink configuration process (or it may have been run automatically before). You need to choose source distribution (not binary). This will set the list of Trees in <tt>'''/sw/etc/fink.conf'''</tt> to have unstable/main at the end. If not you need to add this manually. Because <tt>fink.conf</tt> is owned by root, if you do this manually you will have to do <tt>'''sudo pico /sw/etc/fink.conf'''</tt>. During the configuration process you will also have to choose between the CVS (Concurrent Versions System or Concurrent Versioning System) and rsync update methods. Rsync is a very fast protocol. It will update the description files faster than the old CVS update method. Furthermore, CVS updates are always done from sourceforge.net while rsync updates can be done from a mirror close to you. I found that CVS often stalled trying to access files, though rsync had the disadvantage that sometimes files were not found (and perhaps as CVS uses the master copy the files should be found). Nevertheless, I suggest you use rsync. If you are behind a firewall (even the firewall in a broadband router), you may need to set ProxyPassiveFTP to true to help get around the firewall.
<li> In Terminal type <tt>'''fink selfupdate-rsync'''</tt> This should make sure all the package descriptions are downloaded, and the core packages correctly updated. I found I had to repeat this command several times, trying different mirrors when problems arose with accessing files, before the update succeeded. Fortunately, once a file has been downloaded, if you quit the process (ctrl-C), then on typing the command again, it starts from where it left off.
<li> I also got the following error, and carried out the suggested instructions (I had to use sudo apt-get in each case), which installed some extra packages and seemed to work.<pre> The following inconsistencies found:
Unsatisfied dependency in gettext-tools: gettext (= 0.10.40-19)

Trying to resolve dependencies...
Could not resolve inconsistent dependencies!

Fink isn't sure how to install the above packages safely.
You may be able to fix things by running:

fink scanpackages
apt-get update
apt-get install gettext=0.10.40-25{CODE}
</pre></li></ol>

====Install the Gramps dependencies====

In Terminal, successively type in the following instructions:

sudo fink install pygtk2-py24
sudo fink install gnome-python2-py24
sudo fink install librsvg2-gtk

I found that a number of the files could not be found on the first mirror that was tried, or the files would not download. Sometimes, I could follow the suggestions and get the file from the next mirror that was suggested. However I also quit out of the install process by ctrl-C (twice) and started again. Fortunately files already downloaded are remembered.

Later on, I found that the gramps build process complained about another package missing, so in Terminal I had to type:

sudo fink install gnome-doc-utils

In attempting to resolve some of the glitches, I also installed a number of other packages. These are not essential and did not resolve the issue with the spell checker, but somewhere along the way I seem to have resolved the assert warnings. In Terminal type:

sudo fink install gtkspell2
sudo install gnome-spell
sudo fink install gnome-spell
sudo fink install gnome-python2-py24-dev
sudo fink install gnome-python2-py24-vfsmodule
sudo fink install gtkspell2-dev

====Download and install Gramps====

<ol><li>[http://sourceforge.net/project/showfiles.php?group_id=25770 Download gramps] for example to <tt>'''~/Downloads'''</tt>. On the Gramps page, you need to scroll down to find a file like '''gramps-2.2.6.tar.gz'''.

<li>Unpack the file; assuming you download to the suggested place, in Terminal type:<pre> cd ~/Downloads
tar -xzf gramps-2.2.6.tar.gz
</pre> [According to the fink User's Guide "It is important that you don't use '''StuffIt Expander''' to extract the tar archive. For some reason '''StuffIt''' still can't handle long file names. If '''StuffIt Expander''' already extracted the archive, throw away the folder it created"].

<li>'''Optional:''' You can either install gramps in the default directory (which is '''/usr/local/share/gramps'''), or you can read the instructions in the gramps files about "how to install in a non-default prefix" so that you can install gramps into your users own folder rather than into /usr/local/. One user has found that it is best not to put things into /usr/local as it can be difficult to uninstall them afterwards. The following instructions assume you install in the default directory.

<li>Modify the configuration script in the download directory by changing <tt>'''configure'''</tt>. Replace:<pre> imp.find_module('gnome/ui')</pre>with<pre> imp.find_module('ui', gnome.__path__)</pre> Also replace:

imp.find_module('gtk/glade')

with:

imp.find_module('glade', [imp.find_module('gtk')[1]])

<li>Configure gramps by typing in Terminal:<pre> ./configure</pre>

<li>In the file <tt>'''po/Makefile'''</tt>, which is generated by configure, make sure that <tt>'''GMSGFMT'''</tt> has the value:<pre> GMSGFMT = /sw/bin/msgfmt</pre>[I do not know why this is not detected and set by configure run as above].

<li>Build and install gramps by typing in Terminal:<pre> make
sudo make install</pre>

<li>In one of the updates along the way, I had installed Python version 2.5, which is not good because all the library packages are for 2.4. You will need to switch the default version that Python picks up. In Terminal type:<pre>sudo ln -sf /sw/bin/python2.4 python</pre>

<li>In <tt>'''/usr/local/share/gramps/GrampsWidgets.py'''</tt> put:<pre> try:
INFO_ICON = gtk.STOCK_INFO
except:
INFO_ICON = gtk.STOCK_DIALOG_INFO</pre>Somewhere after <tt>'''import gtk'''</tt> in the section labelled: Constants. Then change every reference to <pre>gtk.STOCK_INFO</pre> to <pre>INFO_ICON</pre></li></ol>

====Start Gramps====

This is how Gramps has to be started each time, because there is no tool to start X11 and Gramps together. One way to get around this is to have the system launch X11 at startup, and then forget about it. This kills one of the steps and takes up little memory (I think).

# Start X11 by double clicking on the X11 icon in Applications/Utilities (or in Applications, depending on the version of Mac OS X).
# Start Gramps, by typing, in xterm: <tt>'''gramps'''</tt>. After a pause "Spelling checker is not installed" appears on the xterm, and then Gramps should start.

== Installing gramps for X11 using MacPorts ==

Right now, I will just get the basic information down as to the troubles I ran into and how I fixed them. I will later put in more detailed instructions on using MacPorts and the rest.

=== Starting ===

So, assuming you have MacPorts installed and updated, you might as well try:
<code>
sudo port install gramps</code>
Now, if you're like me and didn't have GNOME or anything like that installed, calling that command will attempt to go through all of the dependencies and install them all. This will take a while, and you might be at this installing gramps for a couple hours (there are a lot of dependencies)

What I did instead was run <code>
port deps gramps</code>, which listed the major dependencies that gramps has. Then, I installed each separately. They are:
<code>
shared-mime-info
py-gnome
py-bsddb</code>
I installed them in the following order:
# shared-mime-info
# py-bsddb
# py-gnome (the tough one)

=== shared-mime-info ===
In order to successfully install this, I first had to run:<code>
sudo port install p5-xml-sax
sudo port install p5-xml-sax-expat</code>
After that, things installed smoothly

=== py-bsddb ===
This actually installed smoothly on my computer.

=== py-gnome ===
For now, I merely list the libraries and what I did to fix the problem.
# py-gtk2
#* I had to make sure to upgrade expat. After that, it installed fine.
# py-orbit
#* This installed without any problems for me.
# libzvt
#* This package needs "dbus" which in turn needs "xmlto". It appears, however, that "xmlto" is not listed as a dependent of "dbus". Hence, I ran <code>sudo port install xmlto</code> by hand. This installed without any problems on my computer.
#* After installing that, and upgrading gtk2 (do this first), this seems to be installing correctly.
# gnome-desktop
#* This was the next problem for me. I installed ''p5-libxml-perl, p5-xml-simple, py-xml'' by hand, cleaned ''gnome-desktop'', and then tried the installation again. Worked fine!
# gstreamer
#* This was the next problem for me. I installed ''p5-xml-libxslt, py-libxslt by hand'', cleaned gstreamer, and then tried the installation again. Worked fine!
#liboil
#* First, I ran <code>sudo port upgrade gtk-doc</code>
#* Then, I installed the newest version of the liboil library from [http://liboil.freedesktop.org/download/] and then tried to make the liboil library again. (From the manual download). This worked. I would assume it would work for the port version as well.
# nautilus
#* This was the last problem for me. To get around the error, I had to create a soft link for the ''libintl.3.dylib'' file in my /opt/local/lib/ directory.

=== Conclusion ===
Those errors were the ones I ran into. I was able to get gramps to work after that, with some of the same glitches as described below.

== Glitches ==

There are some problems, some from the fink installation.

* Help does not work (clicking Help or FAQ etc on the Help menu does nothing).
* 'Enter' or 'return' does not act as OK for closing windows (the button has to be pressed with the mouse). However Esc does work to exit from the window.
* The browser and email links under the help menu do nothing.
* It is not possible to start Gramps by double clicking on a Mac OS icon, nor by double clicking on a Gramps database that is associated with the application. (It should be possible to create an installation that allows this, just as it is available for OpenOffice).
* The PdfDoc.py plugin cannot be installed because ReportLab is not installed.
** Note, using macports, run <code> sudo port install py-reportlab </code>. This will take care of this problem.
* The LPRDoc.py plugin cannot be loaded because the python bindings for GNOME print are not installed.
* Spell checking does not work (on starting Gramps, an error warning "Spelling checker is not installed" appears on the xterm). The python "bindings for [GNOME print and spell checking] are probably in fink's gnome-python2-desktop-py24 and gnome-python2-extras-py24 packages. Or would be, if fink had them at all, which we don't. They are only viable for for newer versions of gnome itself than fink presently has, or have other dependencies that are not yet satisfiable within fink. We're working on it".
* (Gramps bug 0000940) On starting Gramps, the following assert warnings are output:
<pre>
/usr/local/share/gramps/DbLoader.py:99:
GtkWarning: gtk_file_system_unix_get_folder:
assertion `g_path_is_absolute (filename)' failed
choose.set_current_folder(get_default_dir())
/usr/local/share/gramps/DbLoader.py:153:
GtkWarning: gtk_file_system_unix_get_folder:
assertion `g_path_is_absolute (filename)' failed
choose.set_current_folder(default_dir)
</pre>
* (Gramps bug 0000940) When running gramps, the following warning is output on xterm - this appears to be when I open a new window:

(gramps:516): libglade-WARNING **: unknown property `urgency_hint'
for class `GtkDialog'

* (Gramps bug 0000939) Detection of the availability of gsignal is flawed. In GrampsWidgets.py, there is some code to cater for different versions of gtk.pygtk. I have fink packages pygtk2-gtk-py* version 2.6.3-1 and pygtk2-py* version 2.6.3-2000 installed, so this certainly seems to be version 2.6, and is presumably causing HAVE_2_6 to be set to true. However, on running gramps, I get:

[name G5:~] name% gramps
Traceback (most recent call last):
File "/usr/local/share/gramps/gramps.py", line 97, in ?
import gramps_main
File "/usr/local/share/gramps/gramps_main.py", line 47, in ?
import ViewManager
File "/usr/local/share/gramps/ViewManager.py", line 68, in ?
import GrampsCfg
File "/usr/local/share/gramps/GrampsCfg.py", line 47, in ?
from GrampsWidgets import *
File "/usr/local/share/gramps/GrampsWidgets.py", line 1162, in ?
class MaskedEntry(gtk.Entry):
File "/usr/local/share/gramps/GrampsWidgets.py", line 1216, in MaskedEntry
gsignal('size-allocate', 'override')
NameError: name 'gsignal' is not defined

The problem is worked around as described above. It also seems to work if you replace or follow the line
HAVE_2_6 = gtk.pygtk_version[:2] == (2, 6)
with
HAVE_2_6 = False

* (Gramps-users report 19 Feb 2007) Output of (for example charts) to OpenOffice causes OpenOffice to crash due to a problem with Gramps handling of '&'.
* (Gramps bug 0000938) Import of a GEDCOM file that contains an invalid date of the form 2 DATE BET ABT 1912 AND 1915 causes the date to appear as blank.
* (Gramps-devel mailing list 11 Feb 2007) Gramps aborts at startup with the following error:

File "/usr/local/share/gramps/GrampsWidgets.py", line 2010, in ?
MANDATORY_ICON = gtk.STOCK_INFO
AttributeError: 'module' object has no attribute 'STOCK_INFO'{CODE}

This stock item is added in Gtk 2.8 and fink an older Gtk, for more info see: http://www.pygtk.org/docs/pygtk/gtk-stock-items.html.

This is worked around by patching the application as above.

Mac OS X:Build from source:fink

2007-06-15T04:48:34Z

Tkott: added a section on installing with MacPorts

== Introduction ==

This page describes how to install Gramps on OSX using X11. The process uses fink or a similar program called macports to install the packages that gramps depends on. Gramps does work, although there are some glitches which are described below.

The author of the fink guide thanks the original author from which that part of the guide was written, and for the help of people on the Gramps list for helping them work through the stumbling blocks!

The fink guide applies to Mac OS X 10.4.8, and Gramps 2.2.6, but might work with other versions.

The macports guide applied to Mac OS X 10.4.8 and Gramps 2.2.6, but should work otherwise.

=== General Caveats ===

* As stated above, these instructions were for installing 2.2.6 on Mac OS X 10.4.8, but should work more widely.
* Production of a guide like this should really only be done after repeating the installation from a clean machine, and repeating again till the guide exactly matches the actual process - doing so would take a lot of time; the authors have each only done the installation once, so your experience will almost certainly differ from theirs.
* The process is not very straightforward, and there will almost certainly be problems like unresolved dependencies, files not found on the various servers, download of files just stalls indefinitely and questions asked by scripts to which you don't know the answer. Nevertheless, installation is possible and I think gramps is worth the trouble. I suggest you have a look at the instructions for [http://www.captnswing.net/2004/02/12/nicotine.html|Installing SoulSeek] - this is a similar process, but actually ''SoulSeek'' is easier because it is fully integrated into the fink process. This might give you some idea of the requirements for perseverance. If you don't think you could install ''SoulSeek'' then you certainly won't be able to install Gramps. '''The converse is not true'''

== Installing Gramps on Mac OS X via fink to use X11 ==

* You are installing from the 'unstable' fink tree, so the versions of the packages you install may vary from day to day, and there could be problems with them.

=== Installation instructions ===

==== Install X11 ====

If you have not already installed X11, install it from the Apple OS X installation disks.

====Install Developer Tools====

If you have not already installed the Developer Tools, install them from a recent Apple OS X installation disks (there may be a CD labelled XCode Tools, or an XCode folder on the install DVD). If your installation disk is not very recent, it may be better to download the tools from the [http://developer.apple.com/tools/xcode/ Apple web-site] (free registration required to access the development tools) because some of the build process will not work with an old version of the tools.

====Install and update fink====

This was much more difficult than it should have been. From reading some of the fink mailing lists, I think there may have been some problems with updates to the fink mirrors at the time.

<ol><li> Download the appropriate version of [http://fink.sourceforge.net/download/index.php?phpLang=en fink]. These instructions were tried with fink 0.8.1. You may need the [http://fink.sourceforge.net/doc/users-guide/ Fink User's Guide].
<li> Install fink by opening the disk image and double clicking on the installer.pkg.
<li> You could use FinkCommander to provide a GUI to fink, but it is not worth the trouble, because I wasn't sure that it actually offered all the packages that I wanted, and sometimes did not allow me to type in responses to questions (this is presumably a bug). I suggest you use Terminal. In Terminal type <tt>'''fink self-update'''</tt> This should download package descriptions and update core packages including fink itself. I thought it would be best to do this update before switching from source to binary distribution, but I had to try the whole updating process several times before I actually managed to get it to succeed, so this may be a bad choice.
<li> In Terminal type <tt>'''fink configure'''</tt> This should run the fink configuration process (or it may have been run automatically before). You need to choose source distribution (not binary). This will set the list of Trees in <tt>'''/sw/etc/fink.conf'''</tt> to have unstable/main at the end. If not you need to add this manually. Because <tt>fink.conf</tt> is owned by root, if you do this manually you will have to do <tt>'''sudo pico /sw/etc/fink.conf'''</tt>. During the configuration process you will also have to choose between the CVS (Concurrent Versions System or Concurrent Versioning System) and rsync update methods. Rsync is a very fast protocol. It will update the description files faster than the old CVS update method. Furthermore, CVS updates are always done from sourceforge.net while rsync updates can be done from a mirror close to you. I found that CVS often stalled trying to access files, though rsync had the disadvantage that sometimes files were not found (and perhaps as CVS uses the master copy the files should be found). Nevertheless, I suggest you use rsync. If you are behind a firewall (even the firewall in a broadband router), you may need to set ProxyPassiveFTP to true to help get around the firewall.
<li> In Terminal type <tt>'''fink selfupdate-rsync'''</tt> This should make sure all the package descriptions are downloaded, and the core packages correctly updated. I found I had to repeat this command several times, trying different mirrors when problems arose with accessing files, before the update succeeded. Fortunately, once a file has been downloaded, if you quit the process (ctrl-C), then on typing the command again, it starts from where it left off.
<li> I also got the following error, and carried out the suggested instructions (I had to use sudo apt-get in each case), which installed some extra packages and seemed to work.<pre> The following inconsistencies found:
Unsatisfied dependency in gettext-tools: gettext (= 0.10.40-19)

Trying to resolve dependencies...
Could not resolve inconsistent dependencies!

Fink isn't sure how to install the above packages safely.
You may be able to fix things by running:

fink scanpackages
apt-get update
apt-get install gettext=0.10.40-25{CODE}
</pre></li></ol>

====Install the Gramps dependencies====

In Terminal, successively type in the following instructions:

sudo fink install pygtk2-py24
sudo fink install gnome-python2-py24
sudo fink install librsvg2-gtk

I found that a number of the files could not be found on the first mirror that was tried, or the files would not download. Sometimes, I could follow the suggestions and get the file from the next mirror that was suggested. However I also quit out of the install process by ctrl-C (twice) and started again. Fortunately files already downloaded are remembered.

Later on, I found that the gramps build process complained about another package missing, so in Terminal I had to type:

sudo fink install gnome-doc-utils

In attempting to resolve some of the glitches, I also installed a number of other packages. These are not essential and did not resolve the issue with the spell checker, but somewhere along the way I seem to have resolved the assert warnings. In Terminal type:

sudo fink install gtkspell2
sudo install gnome-spell
sudo fink install gnome-spell
sudo fink install gnome-python2-py24-dev
sudo fink install gnome-python2-py24-vfsmodule
sudo fink install gtkspell2-dev

====Download and install Gramps====

<ol><li>[http://sourceforge.net/project/showfiles.php?group_id=25770 Download gramps] for example to <tt>'''~/Downloads'''</tt>. On the Gramps page, you need to scroll down to find a file like '''gramps-2.2.6.tar.gz'''.

<li>Unpack the file; assuming you download to the suggested place, in Terminal type:<pre> cd ~/Downloads
tar -xzf gramps-2.2.6.tar.gz
</pre> [According to the fink User's Guide "It is important that you don't use '''StuffIt Expander''' to extract the tar archive. For some reason '''StuffIt''' still can't handle long file names. If '''StuffIt Expander''' already extracted the archive, throw away the folder it created"].

<li>'''Optional:''' You can either install gramps in the default directory (which is '''/usr/local/share/gramps'''), or you can read the instructions in the gramps files about "how to install in a non-default prefix" so that you can install gramps into your users own folder rather than into /usr/local/. One user has found that it is best not to put things into /usr/local as it can be difficult to uninstall them afterwards. The following instructions assume you install in the default directory.

<li>Modify the configuration script in the download directory by changing <tt>'''configure'''</tt>. Replace:<pre> imp.find_module('gnome/ui')</pre>with<pre> imp.find_module('ui', gnome.__path__)</pre> Also replace:

imp.find_module('gtk/glade')

with:

imp.find_module('glade', [imp.find_module('gtk')[1]])

<li>Configure gramps by typing in Terminal:<pre> ./configure</pre>

<li>In the file <tt>'''po/Makefile'''</tt>, which is generated by configure, make sure that <tt>'''GMSGFMT'''</tt> has the value:<pre> GMSGFMT = /sw/bin/msgfmt</pre>[I do not know why this is not detected and set by configure run as above].

<li>Build and install gramps by typing in Terminal:<pre> make
sudo make install</pre>

<li>In one of the updates along the way, I had installed Python version 2.5, which is not good because all the library packages are for 2.4. You will need to switch the default version that Python picks up. In Terminal type:<pre>sudo ln -sf /sw/bin/python2.4 python</pre>

<li>In <tt>'''/usr/local/share/gramps/GrampsWidgets.py'''</tt> put:<pre> try:
INFO_ICON = gtk.STOCK_INFO
except:
INFO_ICON = gtk.STOCK_DIALOG_INFO</pre>Somewhere after <tt>'''import gtk'''</tt> in the section labelled: Constants. Then change every reference to <pre>gtk.STOCK_INFO</pre> to <pre>INFO_ICON</pre></li></ol>

====Start Gramps====

This is how Gramps has to be started each time, because there is no tool to start X11 and Gramps together. One way to get around this is to have the system launch X11 at startup, and then forget about it. This kills one of the steps and takes up little memory (I think).

# Start X11 by double clicking on the X11 icon in Applications/Utilities (or in Applications, depending on the version of Mac OS X).
# Start Gramps, by typing, in xterm: <tt>'''gramps'''</tt>. After a pause "Spelling checker is not installed" appears on the xterm, and then Gramps should start.

== Installing gramps for X11 using MacPorts ==

Right now, I will just get the basic information down as to the troubles I ran into and how I fixed them. I will later put in more detailed instructions on using MacPorts and the rest.

=== Starting ===

So, assuming you have MacPorts installed and updated, you might as well try:
<code>
sudo port install gramps</code>
Now, if you're like me and didn't have GNOME or anything like that installed, calling that command will attempt to go through all of the dependencies and install them all. This will take a while, and you might be at this installing gramps for a couple hours (there are a lot of dependencies)

What I did instead was run <code>
port deps gramps</code>, which listed the major dependencies that gramps has. Then, I installed each separately. They are:
<code>
shared-mime-info
py-gnome
py-bsddb</code>
I installed them in the following order:
# shared-mime-info
# py-bsddb
# py-gnome (the tough one)

=== shared-mime-info ===
In order to successfully install this, I first had to run:<code>
sudo port install p5-xml-sax
sudo port install p5-xml-sax-expat</code>
After that, things installed smoothly

=== py-bsddb ===
This actually installed smoothly on my computer.

=== py-gnome ===
For now, I merely list the libraries and what I did to fix the problem.
# py-gtk2
#* I had to make sure to upgrade expat. After that, it installed fine.
# py-orbit
#* This installed without any problems for me.
# libzvt
#* This package needs "dbus" which in turn needs "xmlto". It appears, however, that "xmlto" is not listed as a dependent of "dbus". Hence, I ran <code>sudo port install xmlto</code> by hand. This installed without any problems on my computer.
#* After installing that, and upgrading gtk2 (do this first), this seems to be installing correctly.
# gnome-desktop
#* This was the next problem for me. I installed ''p5-libxml-perl, p5-xml-simple, py-xml'' by hand, cleaned ''gnome-desktop'', and then tried the installation again. Worked fine!
# gstreamer
#* This was the next problem for me. I installed ''p5-xml-libxslt, py-libxslt by hand'', cleaned gstreamer, and then tried the installation again. Worked fine!
#liboil
#* First, I ran <code>sudo port upgrade gtk-doc</code>
#* Then, I installed the newest version of the liboil library from [http://liboil.freedesktop.org/download/] and then tried to make the liboil library again. (From the manual download). This worked. I would assume it would work for the port version as well.
# nautilus
#* This was the last problem for me. To get around the error, I had to create a soft link for the ''libintl.3.dylib'' file in my /opt/local/lib/ directory.

=== Conclusion ===
Those errors were the ones I ran into. I was able to get gramps to work after that, with some of the same glitches as described below.

== Glitches ==

There are some problems, some from the fink installation.

* Help does not work (clicking Help or FAQ etc on the Help menu does nothing).
* 'Enter' or 'return' does not act as OK for closing windows (the button has to be pressed with the mouse). However Esc does work to exit from the window.
* The browser and email links under the help menu do nothing.
* It is not possible to start Gramps by double clicking on a Mac OS icon, nor by double clicking on a Gramps database that is associated with the application. (It should be possible to create an installation that allows this, just as it is available for OpenOffice).
* The PdfDoc.py plugin cannot be installed because ReportLab is not installed.
* The LPRDoc.py plugin cannot be loaded because the python bindings for GNOME print are not installed.
* Spell checking does not work (on starting Gramps, an error warning "Spelling checker is not installed" appears on the xterm). The python "bindings for [GNOME print and spell checking] are probably in fink's gnome-python2-desktop-py24 and gnome-python2-extras-py24 packages. Or would be, if fink had them at all, which we don't. They are only viable for for newer versions of gnome itself than fink presently has, or have other dependencies that are not yet satisfiable within fink. We're working on it".
* (Gramps bug 0000940) On starting Gramps, the following assert warnings are output:
<pre>
/usr/local/share/gramps/DbLoader.py:99:
GtkWarning: gtk_file_system_unix_get_folder:
assertion `g_path_is_absolute (filename)' failed
choose.set_current_folder(get_default_dir())
/usr/local/share/gramps/DbLoader.py:153:
GtkWarning: gtk_file_system_unix_get_folder:
assertion `g_path_is_absolute (filename)' failed
choose.set_current_folder(default_dir)
</pre>
* (Gramps bug 0000940) When running gramps, the following warning is output on xterm - this appears to be when I open a new window:

(gramps:516): libglade-WARNING **: unknown property `urgency_hint'
for class `GtkDialog'

* (Gramps bug 0000939) Detection of the availability of gsignal is flawed. In GrampsWidgets.py, there is some code to cater for different versions of gtk.pygtk. I have fink packages pygtk2-gtk-py* version 2.6.3-1 and pygtk2-py* version 2.6.3-2000 installed, so this certainly seems to be version 2.6, and is presumably causing HAVE_2_6 to be set to true. However, on running gramps, I get:

[name G5:~] name% gramps
Traceback (most recent call last):
File "/usr/local/share/gramps/gramps.py", line 97, in ?
import gramps_main
File "/usr/local/share/gramps/gramps_main.py", line 47, in ?
import ViewManager
File "/usr/local/share/gramps/ViewManager.py", line 68, in ?
import GrampsCfg
File "/usr/local/share/gramps/GrampsCfg.py", line 47, in ?
from GrampsWidgets import *
File "/usr/local/share/gramps/GrampsWidgets.py", line 1162, in ?
class MaskedEntry(gtk.Entry):
File "/usr/local/share/gramps/GrampsWidgets.py", line 1216, in MaskedEntry
gsignal('size-allocate', 'override')
NameError: name 'gsignal' is not defined

The problem is worked around as described above. It also seems to work if you replace or follow the line
HAVE_2_6 = gtk.pygtk_version[:2] == (2, 6)
with
HAVE_2_6 = False

* (Gramps-users report 19 Feb 2007) Output of (for example charts) to OpenOffice causes OpenOffice to crash due to a problem with Gramps handling of '&'.
* (Gramps bug 0000938) Import of a GEDCOM file that contains an invalid date of the form 2 DATE BET ABT 1912 AND 1915 causes the date to appear as blank.
* (Gramps-devel mailing list 11 Feb 2007) Gramps aborts at startup with the following error:

File "/usr/local/share/gramps/GrampsWidgets.py", line 2010, in ?
MANDATORY_ICON = gtk.STOCK_INFO
AttributeError: 'module' object has no attribute 'STOCK_INFO'{CODE}

This stock item is added in Gtk 2.8 and fink an older Gtk, for more info see: http://www.pygtk.org/docs/pygtk/gtk-stock-items.html.

This is worked around by patching the application as above.

Mac OS X:Build from source:Native OS X

2007-06-15T03:53:50Z

Tkott: /* Running */ added info on non-default python install

[[Category:Developers/Packaging]]
== 2.2.x series (Native PPC only) ==

Gramps on OSX native does just about work. It is not as functional as the X11 version (see ) but it does require less dependencies.

=== Caveats ===

* Only a few people are known to have got this to work (let me know if you know different: rjt-gramps (at) thegrindstone.me.uk)
* If you loose your database don't blame me.
* This is in no way a supported port.

'''Note: there is no compiling or any scary geekery necessary to make this work!'''

=== Installing dependencies ===

You will need gtk and pygtk and these in turn require Python 2.4.4. The only packaged builds of pygtk/gtk that I know of are at: [http://sourceforge.net/project/showfiles.php?group_id=175176 http://sourceforge.net/project/showfiles.php?group_id=175176] , these are only for PPC. If you know of any other packaged builds please let me know. The lack of a universal binary package is the only reason why these instructions will not work on Intel Macs.

* install MacPython 2.4.4 from: [http://www.python.org/download/releases/2.4.4/ http://www.python.org/download/releases/2.4.4/]
* install "1.1 (with Glade) for python2.4" from [http://sourceforge.net/project/showfiles.php?group_id=175176 http://sourceforge.net/project/showfiles.php?group_id=175176]

=== Patching gramps ===

Once you unpack gramps you need to make one small change. The pygtk build has a broken cairo so you need to turn off the cairo support in the Pedigree view, otherwise bad things happen.

cd src/DataViews

edit _PedigreeView.py, remove the following lines:

try:
import cairo
cairo_available = True
except:
cairo_available = False

replace them with:

cairo_available = False

=== Running ===

To run GRAMPS from the terminal you need to do the following:

cd src/
python gramps.py

If you would rather have an OS X style bundle (.app) you may follow these steps:

* Using Script Editor save the following AppleScript as an application bundle

<pre>tell application "Terminal" 
do script "Python /Applications/Gramps.app/Contents/Resources/src/gramps.py" 
end tell 
tell application "System Events" 
set visible of process "Terminal" to false 
end tell</pre>

Or, you may download this readymade bundle - [[Media:Gramps.zip|Gramps.app]].

If you have python installed in a different place than /usr/bin, or you have several versions installed in different places (such as /opt/local/bin), then just open the main.scpt file in Script Editor in the Gramps package and edit the script.

* Then, copy the "src" directory from the GRAMPS source code to the Resources directory of Gramps.app.

That is it. This can be used like any other application. However, unless you change the path in the script the bundle must reside in /Applications.

=== Issues ===

I had to export my database from my existing fink based install into gramps XML format and then import it into the native version. I doubt that the two versions will coexist very nicely.
Many things don't work. I know that drag and drop does not work, there are issues with mouse click on menus going missing and anything that calls an external programme will not work e.g. help etc.

User:Tkott

2007-06-13T21:18:36Z

Tkott: New page: I am a new user of Gramps (installed 6/11/07), but I went through a macports install, which I shall be writing up soon. I am putting together my sources of family info into one place, and ...

I am a new user of Gramps (installed 6/11/07), but I went through a macports install, which I shall be writing up soon. I am putting together my sources of family info into one place, and hope to be putting up a website soon.

Feel free to post on my talk page if you have questions about:
* Mac OS X
* Macports install of gramps

I will try to answer your questions, although I might not know the answer!

Tomek

Mac OS X:Build from source

2007-06-13T21:11:01Z

Tkott: Fixed some typos, added description of MacPorts

[[Category:Developers/Packaging]]
There are three different ways of installing Gramps on Mac OS X. The two linked pages provide step by step instructions.

=== Native Mac OS X ===

You can install it as a [[native Mac OS X]] application which means that Gramps windows have the normal appearance of Macintosh Windows. This choice has fewer dependencies on installing other components. However, it has the disadvantage that drag and drop does not work, and there are issues with mouse clicks going missing, which make it much more difficult to enter information like sources which apply to many different people in your family tree. This is also in some ways a less mainstream approach so it may be harder to find help if you get into difficulties.

=== Mac OS X / X11 ===

The other choice is to install it as a [[Mac OS X X11]] application which means that the Gramps windows have an X11 appearance. You could download and install [http://www.openoffice.org/ OpenOffice] which is very easy to do and will show you what an X11 application looks like. Installing OpenOffice will not be wasted, because you will need it to be able to open reports from Gramps.

Another option is to download [http://www.neooffice.org/ NeoOffice], which is a port of OpenOffice using Java so that it looks like a native Mac OS X application.

=== Source Install Options ===

One can always install Gramps from scratch using the source code. This cane be done in one of three ways:
# manually
# using fink
# using [http://www.macports.org/ macports]

==== Source Code ====
If you have all of the dependent libraries installed already, this should be straightforward. Just download the .tar.gz file, unpack it, and follow the INSTALL instructions.

If, however, you do not have the dependencies installed, I would recommend installing Gramps through either Fink or Macports.

==== Fink ====
Installing Gramps as an X11 application is achieved by downloading and installing the packages on which Gramps depends using software called fink. The process is a bit longwinded, but most of the features of Gramps work, and drag and drop and mouse clicks work very well. If you choose this route, you may be able to get some help both from the Gramps community and the fink community. Detailed instructions can be found here: [[Mac OS X X11]].

==== MacPorts ====
MacPorts is essentially a similar type of program to fink. However, it was created (I believe) specifically for the darwin operating system base, upon which Mac OS X is based.

One user (tkott) has gone through the process of installing Gramps through MacPorts and will be updating this section with his installation notes soon.

Mac OS X:Build from source

2007-06-13T20:48:17Z

Tkott:

[[Category:Developers/Packaging]]
There are three different ways of installing Gramps on Mac OS X. The two linked pages provide step by step instructions.

=== Native Mac OS X ===

You can install it as a [[native Mac OS X]] application which means that Gramps windows have the normal appearance of Macintosh Windows. This choice has fewer dependencies on installing other components. However, it has the disadvantage that drag and drop does not work, and there are issues with mouse clicks going missing, which make it much more difficult to enter information like sources which apply to many different people in your family tree. This is also in some ways a less mainstream approach so it may be harder to find help if you get into difficulties.

=== Mac OS X / X11 ===

The other choice is to install it as a [[Mac OS X X11]] application which means that the Gramps windows have an X11 appearance. You could download and install [http://www.openoffice.org/ OpenOffice] which is very easy to do and will show you what an X11 application looks like. Installing OpenOffice will not be wasted, because you will need it to be able to open reports from Gramps.

Another option is to download [http://www.neooffice.org/ NeoOffice], which is a port of OpenOffice using Java so that it looks like a native Mac OS X application.

=== Source Install Options ===

One can always install Gramps from scratch using the source code. This cane be done in one of three ways:
# manually
# using fink
# using [http://www.macports.org/ macports]

==== Source Code ====
If you have all of the dependent libraries installed already, this should be straightforward. Just download the .tar.gz file, unpack it, and follow the INSTALL instructions.

If, however, you do not have the dependencies installed, I would recommend installing Gramps through either Fink or Macports.

==== Fink ====
Installing Gramps as an X11 application is achieved by downloading and installing the packages on which Gramps depends using some software called fink. The process is a bit longwinded, but most of the features of Gramps work, and drag and drop and mouse clicks work very well. If you choose this route, you may be able to get some help both from the Gramps community and the fink community.

==== MacPorts ====
One user (tkott) has gone through the process of installing Gramps through MacPorts and will be updating this section with his installation notes soon.

Mac OS X:Build from source

2007-06-13T20:45:58Z

Tkott:

[[Category:Developers/Packaging]]
There are three different ways of installing Gramps on Mac OS X. The two linked pages provide step by step instructions.

=== Native Mac OS X ===

You can install it as a [[native Mac OS X]] application which means that Gramps windows have the normal appearance of Macintosh Windows. This choice has fewer dependencies on installing other components. However, it has the disadvantage that drag and drop does not work, and there are issues with mouse clicks going missing, which make it much more difficult to enter information like sources which apply to many different people in your family tree. This is also in some ways a less mainstream approach so it may be harder to find help if you get into difficulties.

=== Mac OS X / X11 ===

The other choice is to install it as a [[Mac OS X X11]] application which means that the Gramps windows have an X11 appearance. You could download and install [http://www.openoffice.org/ OpenOffice] which is very easy to do and will show you what an X11 application looks like. Installing OpenOffice will not be wasted, because you will need it to be able to open reports from Gramps.

Another option is to download [http://www.neooffice.org/ NeoOffice], which is a port of OpenOffice using Java so that it looks like a native Mac OS X application.

=== Source Install Options ===

One can always install Gramps from scratch using the source code. This cane be done in one of three ways:
# manually
# using fink
# using [https://www.macports.org/ macports]

==== Source Code ====
If you have all of the dependent libraries installed already, this should be straightforward. Just download the .tar.gz file, unpack it, and follow the INSTALL instructions.

If, however, you do not have the dependencies installed, I would recommend installing Gramps through either Fink or Macports.

==== Fink ====
Installing Gramps as an X11 application is achieved by downloading and installing the packages on which Gramps depends using some software called fink. The process is a bit longwinded, but most of the features of Gramps work, and drag and drop and mouse clicks work very well. If you choose this route, you may be able to get some help both from the Gramps community and the fink community.

==== MacPorts ====
One user (tkott) has gone through the process of installing Gramps through MacPorts and will be updating this section with his installation notes soon.