On Mo, 2011-08-22 at 15:32 +0200, Murray Cumming wrote:
> On Thu, 2011-08-18 at 16:03 +0200, Patrick Ohly wrote:
> > +static string SyncEvolutionDataDir()
> > +{
> > + string dataDir(DATA_DIR);
> > + const char *envvar = getenv("SYNCEVOLUTION_DATA_DIR");
> > + if (envvar) {
> > + dataDir = envvar;
> > + }
> > + return dataDir;
> > +}
> >
> > This new env variable needs to be documented in README.rst. A better
> > place for this
> > function might be in util.h/cpp.
>
> Is there even any need for an environment variable to override the
> default location? Just for testing?
Primarily for testing. A secondary, less important use case is that some
users might not have root access on a machine and thus might be forced
to run pre-compiled binaries in a non-standard location. That works when
setting the env variables right. The HTTP server HOWTO explained that.
I'm running SyncEvolution like that for my own use on estamos.de
That reminds me: syncevo-http-server sets all these env variables when
asked to. SYNCEVOLUTION_DATA_DIR must be added there.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
