On Thu, Jul 03, 2008 at 11:49:54AM +0200, Florian Hubold wrote:
when using gnumed on mandriva it does not find the local
database, which is setup correctly. Gnumed is started either via menu
entry or
in a terminal with "gnumed". After contacting Paul Grinberg it turned out
gnumed needs to be explicitly called with
gnumed --conf-file=/etc/gnumed/gnumed-client.conf
This isn't going to work really well.
IF the user explicitely names a config file (and versions up
to 0.2.8.x needed that for unrelated reasons) that file
needs to be *writable*. The assumption is that the user (or
the package maintainer) better knows what she does if they
make something explicit.
The unrelated reason was that GNUmed would in some
situations fail to tolerate the lack of a writable file for
user preferences.
The latest releases are much more vocal about this in the
user interface. In the devel branch this whole issue is
(supposedly) fixed for good.
then it works as expected. As i understood gnumed parses some paths in
search
for valid configuration files
Yes.
, why doesn't it use the one in /etc?
It does.
Karsten