kconf_update: ensuring it has run

[Marc Mutz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

We already got a few reports for KMail that came from people who copied 
their KDE 2.x kmailrc over the newly created 3.0.0 version after 
upgrading and found that some things didn't work anymore.

There was also a problem with kconf_update running scripts multiple 
times due to permission problems with kconf_updaterc.

Can we possibly make kconf_update
1. be more verbose when it fails (testing scripts is 
   particularly difficult currently: I needed the best part of one hour 
   to find out that I mispelt Id= as ID= and missed the ,perl on the 
   Script= key's value :-( )
2. include information of which conversions have been run in the 
    processed config file, e.g. copy the kconf_updaterc:[app.upd] group 
    to apprc:[kconf_update, so the app can check on startup that all 
    conversions were applied.

KMail uses the kconf_update mechanism quite heavilly and we rely on it 
for much more than shoving some keys between groups. E.g. I have patch 
on my HD that uses kconf_update to convert all identity references in 
kmailrc to use numeric IDs rather than the identity name (to fix the 
obvious problem on renaming identities), complete with creating 
numerical IDs for each identity found.

If this script isn't run, all references to identities will be lost.
What's worse, we plan to introduce the same concept for Kmail's folders.

Marc

- -- 
Marc Mutz <mutz at kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE87qIK3oWD+L2/6DgRAvpGAKD5eVppeRHLEXAE3YRwSZfgIcAXjgCeK2ph
Uv2elBELxWX6EQYDyMsbGio=
=zuPT
-----END PGP SIGNATURE-----