small bug in KDevelop-Setup( suggested solution )

[Peter Buckenleib]

Hi folks,

What do you think about enhancing the startup/setup of KDevelop the following 
way:

Now KDevelop looks for a file "kdeveloprc" in the users config-directory, and 
if there is one, kdevelop thinks that everything is set up consistently and 
starts working. Otherwise the setup-procedure is called.

But if this config-file is totally outdated, as it was created by some old 
(perhaps pre-alpha) version, then pathes may wrong, entries might be missing, 
some entries might be obsolet, and kdevelop gets into trouble (thats what 
happened to me).

Why not add a version-id (might be the CVS-version string) to the config file?

Then kdevelop might see if that is a up-to-date config file that it created 
(if the version-strings in kdeveloprc matches the intenally stored 
versionstring inside kdevelop) or if this config file is something obsolet 
that was not cleaned up correctly when an older version was removed or 
updated, and should not be taken to start normal working without doing an 
actual setup first.

Perhaps this mechanism could be included in a upcomming version of the 
kde-libs, so every newly compiled kde-application could share the benefits?

regards

Peter

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«