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

[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.

Unlike some other big distributions, we aren't shipping both KDE 3 and 4 
versions of the same application in Fedora. This mailtransports.upd issue was 
the _only_ case we encountered of KDE 4 apps/libs breaking KDE 3 ones.

> 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.

Well, consider that:
* kdepim is not available in 4.0, so the latest stable version is 3.5.8;
* the latest stable version of KDE is 4.0.0 (soon to be 4.0.1) and requires 
kdepimlibs;
* thus, people using the latest stable versions of everything will be running 
kdepimlibs 4.0.x and kdepim 3.5.x;
* the default KDEHOME directory in the upstream tarballs is ~/.kde for both 
KDE 3 and 4;
* mailtransports.upd breaks the kdepim 3 configuration if run on it;
thus, (re)enabling this kconf_update script means breaking the default 
configuration (again) for users running the latest stable versions.

Now if you think this is acceptable, feel free to revert my commit. _Our_ 
(Fedora's) packages won't be the broken ones. ;-)

        Kevin Kofler
_______________________________________________
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/