[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Re: Packages
From: |
Ian Haywood |
Subject: |
Re: [Gnumed-devel] Re: Packages |
Date: |
Wed, 25 Feb 2004 20:51:22 +1100 |
User-agent: |
Mutt/1.5.5.1+cvs20040105i |
On Wed, Feb 25, 2004 at 09:33:29AM +0100, Karsten Hilbert wrote:
> Aha ! Not a bad thought :-))
>
> *Then* $GNUMED_DIR isn't even needed anymore ... Simply start
> the client with
> --conf-file=/my/strange/path/to/gnumed.conf
> and you are set.
> I like that. Less options achieving the same end.
> What do other people think ?
I agree.
My only nitpick is the chicken-and-egg scenario: we need gmCfg to
read the config file, we need the config file to find gmCfg....
Solutions:
- inline the code into gnumed.py (~200 lines)
- use Python's own ConfigParser class.
We still haven't resolved the default install location issue.
I vote for /usr/share/gnumed/, mainly because that's
Debian policy, and escapes Python upgrade traumas.
Ian
--
PGP public key E750652E at wwwkeys.pgp.net
9BF0 67B7 F84F F7EE 0C42 C063 28FC BC52 E750 652E
signature.asc
Description: Digital signature
- [Gnumed-devel] Re: Packages, (continued)
Re: [Gnumed-devel] Packages, Karsten Hilbert, 2004/02/22
Re: [Gnumed-devel] Packages, Karsten Hilbert, 2004/02/23
[Gnumed-devel] Re: Packages, Andreas Tille, 2004/02/24
Re: [Gnumed-devel] Re: Packages, Karsten Hilbert, 2004/02/25
Re: [Gnumed-devel] Re: Packages,
Ian Haywood <=
Re: [Gnumed-devel] Re: Packages, David Grant, 2004/02/25
[Gnumed-devel] Re: Packages, Andreas Tille, 2004/02/26
Re: [Gnumed-devel] Re: Packages, David Grant, 2004/02/26
[Gnumed-devel] Re: Packages, Andreas Tille, 2004/02/26
Re: [Gnumed-devel] Re: Packages, Karsten Hilbert, 2004/02/25
[Gnumed-devel] Re: Packages, Andreas Tille, 2004/02/26
Re: [Gnumed-devel] Packages, Karsten Hilbert, 2004/02/22