Re: [Gnumed-devel] install instructions

[Hilmar Berger]

> That way GNUMED_DIR/etc/ is a
> standard path in which these datafiles will be searched. 
> > The Setup-Plugin and the DrugBrowser make use of this mechanism to find
> > various config files. So if these two plugins don't do what want, check
> the
> > log-file if they find the config files. 
> Shouldn't we then add logic to these modules to make them find
> client/etc/ in a stock CVS tree ?
We could do that, but we should not add to much "standard locations" to the
search path for config files. 
IMHO there are already too many dirs we search config files in. 
While running from CVS we certainly need 
~/.<basename>
(/etc/<basename>/ - not used if everything is in the CVS-tree)
GNUMED_DIR/client/etc
(+ a fallback for windows)

Once gnumed is properly installed we will need
~/.<basename>
/etc/<basename>/
GNUMED_DIR/client/etc (as fallback)
(+ a fallback for windows)

Right now we search /etc, too. This might lead to name confusions. It's
better to separate gnumed config files.

So what we need is a proper way to find the GNUMED_DIR in both cases, either
set from the environment
or by some logic within gmCfg. If we assume that gnumed.py will always be in
client/wxpython, then it will be quite easy to determine the base dir. Is
this assumption correct ?

Hilmar

-- 
NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien...
Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService

Jetzt kostenlos anmelden unter http://www.gmx.net

+++ GMX - die erste Adresse für Mail, Message, More! +++