Re: [Gnumed-devel] gnumed not finding local db caused by not using correct config file

[Karsten Hilbert]

On Thu, Jul 10, 2008 at 11:25:09AM +0200, Karsten Hilbert wrote:

> Two general principles apply:
> 
> There should be a writable ~/.gnumed/gnumed.conf, even if
> empty. The shell script /usr/bin/gnumed takes care of that
> (at least the one we ship).
> 
> IF --conf-file is given that file needs to be writable, too
> (at least before 0.2.8.10 which is about to be released).

Oh, and perhaps there's a misconception: GNUmed 0.2.8.x uses
the first file it finds among the candidates it searches
for. So if you use --conf-file=... this file needs to
contain all the information, profiles and all. GNUmed cannot
collate several config sources.

0.2.9, of course, supports reading data from several sources
such that e.g. profiles can be configured in
/etc/gnumed/gnumed-client.conf AND ~/.gnumed/gnumed.conf.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346