Re: [Gramps-devel] Installing gramps

[Peter L. <pet...@te...>]

Den Wednesday 16 January 2008 21.33.19 skrev James G. Sack (jim):
> Peter Landgren wrote:
> >> 2008/1/16, Peter Landgren <pet...@te...>:
> >>> Hi,
> >>>
> >>> In the wiki about 3.o it says:
> >>> Do not install the development version. That is, do not type make
> >>> install Is this still valid?
> >>
> >> Of course. You are a developer and do what you want (it is a free world
> >> after all), but we don't want common people to start complaining because
> >> they destroy their package system info and/or gramps 2.x setup.
> >
> > Yes, I understand that.
> >
> >> If I do it, it seems to work with one exception.
> >>
> >>> In order to get the translation to work I have to change
> >>> loc = "/usr/share/locale"
> >>> to
> >>> loc = "/usr/local/share/locale"
> >>> in src/gramps.py
> >>>
> >>> ./configure installs in /usr/local/...
> >>>
> >>> But gramsp.py is obviously looking for the translation in
> >>> /usr/share/... (Same thing of course if  I just install in /po)
> >>
> >> You can pass variables to autogen to set install and language database,
> >> see the INSTALL file.
> >> eg --prefix=/usr
> >
> > It does not matter what --prefix I use. Gramps always look for
> > translations in /usr/share/locale/...
> >
> > The reason is that the shell gramps(.sh), which I execute if  I make
> > install, does not define the variabel GRAMPSI18N whis is used in
> > gramps.py to determine where to look for translations. That confused me.
> > So the shell gramps(.sh) is not ready yet? It does som in 2.2.10
>
> Have you tried setting the environment variable manually?
>
> For example with a bash shell
>   export GRAMPSI18N="/usr/local/share/locale"
> or
>   export GRAMPSI18N=~/grampswork/locale
> (or something like that)
>
> prior to running the rest of the commands.
>
jim,

Yes that works fine.
/Peter