From: dams <da...@id...> - 2002-10-16 16:14:17
|
"Jason Long" <jl...@me...> writes: > I apologize for not responding earlier. I've been delaying because I haven't > really decided yet. :) > > However, I think our projects do have slightly different scopes. Here's how > I would explain it, and be sure to correct me if I am mistaken. > > libconf- > provides a library for creating / manipulating a configuration file. It > will know about the different formats. The user has to specify what file the > configuration setting is in, but doesn't need to know about the internal > format of the file. > > Config4GNU- > tries to provide front-ends for accessing configuration settings for the > whole system. Settings from all sorts of different files will be accessible > through a hierarchical data model. Users who want to make a setting change > don't need to know what file it's actually stored in or what the format of > the file. However, Config4GNU must know about the file and what format it's > in. well, that would be true if libconf was alone :) But libconf is only a layer, another layer will be built on top of it, to abstract the location and the unicity of the information. > > That said, I think there's a great opportunity for collaberation here. The > way I see it, libconf could provide all of the parsing of and manipulation > of configuration files for Config4GNU. ok, why not :) right now the templates supported are : XF86Config Sshd Samba Shell (a tons of files are supported with this template then) Apache Values_section (idem, this is a generic template) I think we are moving faster than you on the first layer, maybe it would be good that config4gnu provides the upper layer Now we have to discuss about this layer :) What about some irc discussion? |