= To build the rpm from source =
A better approach to installing the binary rpm is to build the package from source, this will build gramps using the package versions that you have installed. The [http://download .fedora.redhat.com/pub/fedora/linux/extras/development/SRPMS/|SRPMS] directory contains the source rpm for the latest development build. Download this rpm, install it and build your own binary using the fedora release (in this case fc6) you're running, as the build environment.
== To build the
rpm as non-root (recommended method) ==
Install the build environment in the users directory. '''su -c 'yum install rpmdevtools''''
Login as a 'normal' user and run '''rpmdev- setuptree''' . This will silently create the 'rpmbuild/' tree in the users home directory (instead of using ''usr/src/redhat'' )
Download the source rpm, for this example it will be ''' wget <nowiki>http://download.fedora.redhat.com/pub/fedora/linux/extras/development/SRPMS/gramps- 2. 2.4-3.fc7.src.rpm</ nowiki>''' or use your browser on the [http:// download.fedora.redhat .com/pub/fedora/linux/extras/development/SRPMS/gramps-2.2.4-3.fc7.src.rpm link]
'''rpmbuild -- rebuild gramps- 2.2.4-3.fc7.src.rpm ''' (additional packages may be required at this step - see ''Problems with the build'' below)
su - c 'yum localinstall / home/ <user>/ rpmbuild/ RPMS/noarch/gramps- 2. 2. 4-3. noarch. rpm'''' (use yum to install the rpm)
=== Problems with the build ===
Build errors: such as ''unpackaged files'' etc: The remedy for any of these errors will vary depending on circumstances, ie; there are no easy answers. '''Read the error message carefully''', copy a relevant part of the message string, and search the net. The chances are very good that the problem has been encountered before and a solution exists. If that fails and you're still keen, try the [http://sourceforge.net/mail/?group_id=25770|gramps mailing lists.]
*adding the following line on top of the spec file, /usr/src/redhat//SPEC/gramps.spec: ''%define _unpackaged_files_terminate_build 0'' is a temporary solution provided from the [http://www.rpm.org/hintskinks/unpackaged-files/|rpm.org] lists. Remember, the file will still need packaging, the difference is the build will complete, or the next error will abort it. You'll just be a step closer to knowing how to fix it, or phrasing the question ;-)
= To build an rpm from SVN =