[kdepim-users] Fwd: Tool assisting with the migration from KDE 3 to KDE 4 (was: Re: [kde-promo] bad mood in german kde usenet group)

[Ingo Klöcker]

Forwarding (I snipped the disclaimer) to kde-pim and kdepim-users since 
both audiences are surely interested in your tool, AJ.

The tool the below message talks about can be found at
http://www.kde-apps.org/content/show.php/KDE3TO4?content=85769


Regards,
Ingo

----------  Forwarded Message  ----------

Subject: Re: [kde-promo] bad mood in german kde usenet group
Date: Monday 04 August 2008
From: AJ Venter <AJ.Venter at datacash.co.za>
To: KDE Promo <kde-promo at kde.org>

Hi all,
>> There's a tool on kde-apps helping with this.
Well I wrote that tool so if you try it, I would very much appreciate
feedback :)

>I can assure you that the KDE PIM developers definitely know about
this. 
>At least with KMail we have been changing the configuration with every
minor release. :-)

>Anyway, kconf_update only works with existing configuration files. If
the old KDE 3 settings live in ~/.kde and the new >KDE 4 settings live
in ~/.kde4 then it is impossible for kconf_update to do its work because
it knows nothing about the >old settings in ~/.kde. I guess the
distributors have made provisions for copying ~/.kde to ~/.kde4 (or did
KDE already >make those provisions?), but maybe they've missed
something.

The major reason why several distro's did it this way is to allow KDE3
and KDE4 to exist in parallel without issues, especially since most of
them shipped 4.0 - and apps like KDEPIM weren't ported yet. I'm not
going to get into the flamewar that the fedora guys tried to spark with
me about kde3to4 (they didn't separate them - and thought doing so was a
cop-out with more bad than good results). 
Personally I am of the opinion that the scale of migration is too big
and too many settings won't work natively so it's better not to try and
share configs but my advice to fedora users and others whose distro's do
this was to back up their old .kde FIRST and THEN install the KDE4
distro, which would allow kde3to4 to work. 
I believe the scale of the migration is such that a specialized tool
that knows how to migrate most things, and is modular enough to deal
with edge-cases correctly is the best approach (if I didn't, I wouldn't
be trying to write one).

As I have mentioned before, I am hoping to get this program stable and
functional enough to be included into KDE 4.2 (I was too late to try for
4.1) but in the meantime it is there, and I can confirm that I have
personally used it for KDEPIM apps now and it works fairly well - the
remaining glitches should be handled in the applications though I think.


Of course there could well be room to expand on it and add a module to
convert everything so you can be accessing the same accounts etc. but be
migrated to akonadi after running the wizard but that is not there yet
and will take some serious experimentation to get right (some help from
the devs would be invaluable to make it work too).


Ciao
A.J.

-------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20080804/8acbfcc9/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM users mailing list
kdepim-users at kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users