2,037
edits
Changes
m
If you are See [[Getting_started_with_GRAMPS_development#Run_GRAMPS_from_the_source|running Linux and a variation of Debian (Ubuntu), then you can download Gramps from source]] for details to make the .deb file and install it directlycode work.
Otherwise, you should download the tar.gz file. Here is the basic installation instructions, assuming that the tar.gz file is in your current directory:== Running parallel versions of trunk and branches ==
tar xfz gramps-2.90.0-beta.tar.gz cd gramps-2.90.0-beta ./configure --prefix=/usr/local make su -c "make install" You can then run /usr/local/bin/gramps Warning: you will not be able to load translations on /usr/local/share/locale, because you will load /usr/share/locale, which could be translations for stable release (set on gramps.py).You may generate a custom launcher by adding this line: export GRAMPSI18N=/usr/local/share/localeif you want to use an other path, you may add this line: export GRAMPSI18N=@prefix@/share/localeon current gramps.sh.in (source file) before compillation and installation. == running parallel versions of trunk and branches == As stated in '''Installing GRAMPS 3trunk''', you can only have a dedicated gramps.mo file on /usr/share/local/xx/.. . If you want to have both the trunk and branches version with separate translations, consider using some '''[http://en.wikipedia.org/wiki/Comparison_of_platform_virtual_machines Virtual Machines]'''.
→Installing GRAMPS Trunk
GRAMPS trunk is the newest version of GRAMPS, but it is under development. You can help by trying this version and reporting feedback and bugs. Before embarking on this you should first read this page.
{{man warn|Warning:|A word of caution: trunk is currently considered a ''development version'' and not for use on your real data. You can test trunk on a copy of your data though. See below for more details.}}
You should not ''install'' GRAMPS trunk as that will overwrite your regular GRAMPS. However, you can download and compile trunk locally, largely without interfering with your regular GRAMPS. Subtle interactions are easy to resolve for developers.
Yes! You could:
# Help write documentation on how to use GRAMPS trunk. See [[Gramps 3.2 4 Wiki Manual]]
# Help translate GRAMPS into another language. See [[Portal:Translators|Internationalization]]
# Test and follow-up on issues in the tracker. See http://bugs.gramps-project.org/
Now that you have read all of the precautions, you are ready to begin exploring GRAMPS trunk.
* '''Windows systems''': follow the directions at http://www.dancingpaper.com/gramps/?.
* '''Unix-like systems''': follow the rest of this page.
The easiest method of getting the beta /trunk version is to download it from http://gramps.svn.sourceforge.net/projectviewvc/gramps/showfilestrunk/ using the link at the bottom of the page called '''[http://gramps.phpsvn.sourceforge.net/viewvc/gramps/trunk/?group_idview=25770 under '''Unstabletar Download GNU tarball]'''. This is easy to get and installdownload, but it is probably a few weeks old. If you want to get the freshest code, and you'll will have to do a little more work. See [[Running a development version of Gramps]].
At the moment I experiment with this setup:
** VM1: Linux Mint : on this machine I build and installed trunk. This means running ./autogen script, make AND do a make install (as root)
** VM2: Fedora 8 : on this machine I build and installed branches. This means running ./autogen script, make AND do a make install (as root)
== See also ==
* [[$GRAMPSHOME]]
* [[Installation alternatives]]
[[Category:Developers/General]]
