[Kde-pim] branches/KDE/4.0/kdepimlibs/mailtransport

[Tom Albers]

Op Saturday 26 January 2008 15:08 schreef u:
> The problem with the kconf_update script is pretty easy to reproduce, assuming 
> a shared .kde for KDE 3 and 4 (as Fedora is set up):
> 1. Configure your KDE 3 KMail (set up your accounts).
> 2. Install KDE 4 kdepimlibs.
> 3. Run KDE 3 KMail again and watch how all your account configuration has been 
> messed up (the script doesn't _copy_ it to the new values, it _moves_ them, 
> so it completely breaks KDE-3-based kdepim (3.5 or enterprise shouldn't 
> matter)).
> 
> We've been working around this in Fedora by simply removing the offending 
> script during our package builds. Are we the only distribution using a 
> shared .kde for everything?
> 
>         Kevin Kofler

AFAIK yes. the config files are not backwards compatible. So whenever a 4 app changes the config file, a 3 app can break on that.

And in this case it will indeed break. I'm open to other opinions, but for now I think the commit should be reverted and be kept at distro level. Because kdepimlibs is released, and mailtransport can be used by more applications than the unreleased kdepim. Those applications would like have valid settings, converted from kmail3.

Toma
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/