An analysis about a generic desktop application configuration management system

[Avery Pennarun]

On Mon, Apr 11, 2005 at 06:44:06PM -0400, Maks Orlovich wrote:
> And frankly, looking at the KDE4 timeline, and your lofty list of goals
> that's not very likely (particularly the well-testedness)

Where is the KDE4 timeline?  I can't find it in the usual place I look:

	http://developer.kde.org/development-versions/

The prevailing suggestion for a shared configuration system, ie. one in
which you talk to a config daemon using D-BUS, appears to me like you
wouldn't have to change the KConfig API or ABI in order to implement it.
That reduces your potential problems quite a lot, I think.  You still
wouldn't want to do it at the last minute - bugs in KConfig will obviously
affect the whole system - but at least it seems clear that *fixing* the bugs
would require changing only kdelibs implementation, not API, which is
allowed until the deep freeze phase.

Thanks,

Avery