From: John R. <jr...@ce...> - 2013-03-11 04:02:18
|
On Mar 10, 2013, at 4:11 PM, Nick Hall <nic...@ho...> wrote: > On 10/03/13 20:29, John Ralls wrote: >> On Mar 10, 2013, at 7:40 AM, Nick Hall <nic...@ho...> wrote: >>> Do we still need the GRAMPS_DATA environment variable? If so, should we rename it to GRAMPS_PREFIX (or GRAMPS_SHARE)? >> Yes, to allow the path to be relocatable. That's the whole point of this, remember? I have no particular attachment to the name, so if we call the file some variation of 'resources', perhaps GRAMPS_RESOURCES would be a better name for the environment variable. > > I seem to be missing something here. I thought it was about running multiple installed versions of Gramps (which I never saw the point of). We were trying to avoid search for the resources a runtime, so we wanted to get the packager or installation program to write the resource location somewhere at install-time. > > Having a environment variable would be one solution. I was suggesting that a file be an alternative. > > Once Gramps is installed we know where the resources are. I don't think we need the user to be able to change the location via an environment variable. Or is this for developers? Ah, that's what you're missing. On a mac there is no installation program. The app is all together in a special directory structure called a bundle which looks like a single file to the user, and which the user can drag around from place to place at whim. It's therefore necessary to find the resources at startup every time. Regards, John Ralls |