Don't implement config functionality

Concerning the messages about the prospecive kde-debian System Tool. How it 
should look like, integrate, best language etc. And how it is not fun to 
maintain tools for every package one wants to configure:

IMHO the only real solution is a frontend that does not need a new module for 
each new thing that one wants to configure. So that no time needs to be used 
hardcoding any package specifics.

This can be accomplished if  the specifics are handled for example by the 
config4gnu [1] framework. Using it as the backend allows focusing on all the 
nice usability and eye candy for the frontend. (just like with kdebconf)

And if time goes into improving config4gnu, writing initial xml definitions 
for new packages, or even a perl/python/* syntax parser for it, it is well 
spent because any other frontend benefits also. You will benefit in the same 
way from any other contribution to CFG. And if for example the CC frontend is 
droped for a KAdmin frontend in the future the work won't be lost.

Having different frontends to have different (G)UIs is ok but each GUI having 
to maintain modules for each package just not. What do you think?

May a Control Center module to integrate the Config4gnu nodes be sufficient? 
It could be based on a nice html view of CFGs xml-config-representation.

-Christian


[1]  http://linuxwiki.de/Config4Gnu/EnglishFAQ