[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: [PATCH] KMail kconf_update checks to prevent unapplied updates
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2002-08-15 22:57:14
[Download RAW message or body]

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

On Thursday 15 August 2002 23:59, Marc Mutz wrote:
> I've already comitted changes to make the 3.0 -> 3.1 update scripts
> idempotent. This is the critical part of the patch. It adds
> KConfig::checkUpdate() calls for all updates since 3.0 (Ingo, you
> might want to add the kpgp ones).

But where? The update checks would have to be in every program which 
uses kpgp (so far KMail and KNode). Or can I place them in the 
constructor of KPgp::Module?

> Committing this means that all three update scripts are run again for
> those of us that don't have a [$Version] group in their kmailrc and
> are running HEAD (basically everyone that didn't update from 3.0
> straight to HEAD in the last weeks). That's why I made the scripts
> idempotent, of course.
>
> So, basically, I want you to peer-review the scripts before i commit
> this change.

The three update scripts act trivially on my already updated kmailrc. 
Good.

Regards,
Ingo

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

iD8DBQE9XDHPGnR+RTDgudgRAvOCAJ9MZHIsDAWgU57km01GQem5yQupKwCfQdH7
xTnfH2QKqyJDun3eZHCRCFg=
=/t+r
-----END PGP SIGNATURE-----

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]