18 Jul
2012
18 Jul
'12
1:52 p.m.
Ah, that explains a lot. I'll give it a try and
report back.
The migratekde3 script should be _optional_ for the user to run. Lots of
times I DO NOT WANT the old .kde settings migrated and just want to start with a
clean slate. This is one area where I don't want magic scripts outthinking the
user. We should provide NOTICE of the migratekde3 script but let the user
CHOOSE whether to run it :)
The updated FAQ in the help handbook index references the migratekde3 script (question
4.15).
Unlike the r14-xdg-update script, which is necessary, we don't want to automate using
the migratekde3 script anywhere. There is no way to predict whether a person is migrating
from an old KDE3 profile. I have tested the migratekde3 script fairly well, but like any
software, only through my perspective. I don't use other distros and I don't know
what quirks or corner cases might exist with other distros. The latest version now
recognizes ~/.kdemod3 as a KDE3 profile, thanks to your help. As I mentioned, We should
consider treating Trinity <= 3.5.12 as a KDE3 profile because we did not start serious
or massive renaming until 3.5.13. But I don't have a 3.5.12 or 3.5.11 setup to test
migratekde3. Thus far, you're the only person who can help with that. :)
Darrell