dams wrote: > Luis Ortega <[EMAIL PROTECTED]> said: >> >> Originally, when I checked the wiki page on libconf I >> felt that it would be more interesting if the config >> information was stored in XML. That way, with some >> API, the configuration modules could be written in any >> language, not necessarily Perl. If anyone feels more >> comfortable in, say, Python one could more easily >> contribute modules. And in the case of Python the >> interpreter would be readily in the basic distro. And >> IIRC it is also available in Gentoo. > > libconf doesn't store the config information elsewhere than where they > are - in the config files. Libconf
In the end, there must only be one copy of the configuration information (any other system with meta-configuration eventually has problems with diverging configurations). So, if you want the configuration stored in XML or LDAP, it means the application needs to be using that directly. For applications where configuration can be stored in LDAP (such as Postfix canonical maps etc), the backend should be capable of supporting this, but at present most systems capable of reading configuration from LDAP still require a config file to tell them where to find the LDAP server (among other things). This will change I think, as the use of DNS to locate services becomes more popular (ie Kerberos-style SRV records). > provides a mapping of these > information into a convenient perl structure. It is planed to have an > xml output, and a ldap output. You would then be able to ask libconf to > write an xml file from a standard config file. Or to feed a ldap base. I think the big thing is that the API for frontends needs to be defined, as perl structeres aren't that portable (for instance, consider a remote Windows front-end ...). > > If you think this should be done in priority, I can work on it soon. But > we should agere on a dtd then. Well, what's the XML going to be used for ... in some cases (if configuration in xml is supported) the DTDs should exist already. Regards, Buchan
