gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] gnumed not finding local db caused by not using corre


From: Florian Hubold
Subject: Re: [Gnumed-devel] gnumed not finding local db caused by not using correct config file
Date: Tue, 08 Jul 2008 18:32:04 +0200
User-agent: Thunderbird 2.0.0.14 (X11/20080629)

Karsten Hilbert schrieb:
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
Well, actually you do not give any solution to the problem mentioned.
I still need to explicitly tell it which config file to use. If i don't,
then it does not offer the local db. If i do, it can be chosen in gnumed.
If you say it should use the client config in /etc/gnumed by default,
why does it make a difference?
And this also implies that, if it should use the one in /etc/gnumed
without explicitly telling it, this doesn't have to be writable for the user. Why?

The other option (trying out the devel branch) does not sound real
good for stable packages. But i'll try that out to see if there is any difference.
Is there any particular branch to try, or should i go for the trunk?

After all the only conclusion for me is that with gnumed 0.2.9 this
"problem" should not be there anymore?


Regards

Florian Hubold






reply via email to

[Prev in Thread] Current Thread [Next in Thread]