Assuring konf_update has run successfully (was: Re: Bug#45444: From: always uses default identity)

[Marc Mutz]

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

On Saturday 20 July 2002 20:24, Allan Sandfeld Jensen wrote:
<snip>
> Comparing the code and the configuration I can even tell you what it
> is. uoid is not unique.
<snip>
> uoid=0
<snip>

Now tell, me: You didn't copy an old config file over the new one 
without letting kconf_upadte see it, now didn't you? ;-)

I think KMail (using only kconf_update scipts to make changes in the 
config file layout) now clearly shows that we need to have a way to 
make sure that kconf_update has been run successfully on the config 
file and refuse to start the application if it's not the case. That's 
something that has to go into KConfig's core. It would be rediculous to 
require every app that employs kconf_update to develop a protecttion 
scheme against missing updates for itself.

Marc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9Ob1y3oWD+L2/6DgRAi3eAJ47ulppQXqFRLWuiKJ4AVTzzW0tqQCgw4Ep
6YovC7c0TA2rWo2rD5J8H5c=
=ShWc
-----END PGP SIGNATURE-----