https://bugs.kde.org/show_bug.cgi?id=169827





--- Comment #12 from Kevin Krammer <kevin krammer gmx at>  2009-04-24 21:26:35 
---
(In reply to comment #11)

> Just now I tried manually copying the ~/.kde/share/apps/kmail,
> ~/.kde/share/config/kmailrc to the relevant places under ~/.kde4, and then
> started up KDE4 KMail.  It appears that everything (filters, sending/receiving
> accounts, mail folders, etc.) apart from identities was successfully 
> imported. 

If you copy the emailidentities file directly, it might still work.
If there was something to import KMail would have done that during its startup.

> I'm still not sure why this feature was marked as RESOLVED/DOWNSTREAM.  Why
> should it be the responsibility of vendors to provide the import tool?

They don't have to if the allow Upstream(KDE) to use its own upgrade mechanism.
However, if a distributor changes code of one KDE version to behave different
than the other KDE version, they'll have to provide for a migration path
compensating this additional difference.

> Only
> the KMail developers know the difference in kmailrc file formats between KDE3
> and KDE4.  There's no need for each vendor to code its own importer which does
> the exact same thing.

Right. That's why there are respective scripts for KDE's config upgrade
mechanism.
Vendors only need to code their own importer/migrator if they change KDE in a
ways that makes it impossible for KDE's migrator to work.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-bugs

Reply via email to