Re: MidgardConfig comments (Was: [midgard-dev] Automake and directories)

Hi,

We should start turning this conversation into documentation in the
code and on the wiki. There's been much talk but not many hard
decisions. We should nail down at least the following (with my
suggestions in parenthesis):

0) Roadmap for the new configuration mechanism
   (beta in 1.8, stable in 1.9)

1) Format of the configuration files
   (the GKeyFile format, perhaps using the real GKeyFile parser later on)

2) Location of the configuration files
   (SYSCONFDIR/midgard/conf.d/*.conf and $HOME/.midgard/conf.d/*.conf)

3) The API to read and construct configuration objects
    (See my MidgardConfig proposal a few messages ago)

4) The API to use the configuration to create a connection
    (See my MidgardConnection proposal a few messages ago)

On 2/19/06, Piotras <[email protected]> wrote:
> OK. Should we additionally check for existing possible extension in name?

Better if we didn't. If someone asks for configuration named
"foo.conf", then we should look for a file named
"/etc/midgard/conf.d/foo.conf.conf". :-)

> Yes, I can not focus on log files only now.

OK. We can postpone the log discussion to another thread.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - [email protected]
Software craftsmanship, JCR consulting, and Java development