Cristian Rodríguez wrote:
El 22/01/13 13:34, Ken Schneider - openSUSE escribió:
Having config files is ugly. What a profound statement to make on a highly configurable OS.
NO, having configuration files is fine, as long they are parsed or generated directly by the program itself.
I believe this is the message that created the controversy. To me, and apparently to most other people reading it, it implies two things: (1) every program has the ability to write as well as read its own configuration file(s) (2) no other program is allowed to write a configuration file (else if they do it is 'ugly') People have objected to both of these implications and given counterexamples. Perhaps it would be good for Cristian to state exactly what he did mean. It still isn't clear to me for instance whether he really did mean (2), so that using YaST or a desktop config program to modify configurtion would be impossible (except by modifying YaST to invoke the actual program to edit its own config, which IMHO leads to a pretty complex infrastructure - essentially an object bus - I'd be interested to see an example) There's also the separate issue of the format of config files. It clearly makes sense to have a restricted set of formats that used shared parser and producer code. And to me it makes sense to have a format that is easy for users to understand (e.g. not XML). But there are reasonable alternatives to ini format, and it is possible to use a shared parser that can handle multiple formats automatically. So I don't think it's a question with a clear-cut answer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org