New configuration backends for Samba 3 SoC project

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Metze,

> And the interface should use a context structure that needs 
> to be passed to each function, so that we get rid of
> global var (or for a first step hide them in the
> smb.conf backend).
> 
> As a side effect this would allow us to have 
> different config contexts for different things...(maybe
> usefull in samba4 later).

Hmmm...I wonder if we could use this approach to solve
the variables and include files.  The CONFIG_CTX * might be
able to implement Volker's Variable Environment solution.

> I had a quick look at the www.libelektra.org the gui looks 
> very nice a bit like the windows registry editor:-) But I
> think we should not depend on it in samba...
>
> What we could do is orient our interface on the lelektra 
> one, so that writting an libelektra-samba.so would be just
> wrapping our interface.
> 
> So admin tools can access via the elektra interface, but 
> samba directly uses its own interface.

I'm not interested in adding a lot of development overhead
first time around.  I'm willing to toss the wrapper layer
and requirement libelektra for the SoC project.  We need
to decide early on if libelektra will or will not work for
our use.

Long term (if this does get integrated into the Samba tree),
I agree with you.  But that is an easy change later on.





cheers, jerry
=====================================================================
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEfIYbIR7qMdg1EfYRAsEDAJ9A3wCs02A/Dbxp583RnHC8i1ZqWQCgkkYV
5rxDof2d6TSGWSudRmi0EQQ=
=WzZm
-----END PGP SIGNATURE-----