27 Jul
2012
27 Jul
'12
4:23 a.m.
On 07/18/2012 03:52 PM, Darrell Anderson wrote:
Darrell,
Here is another data-point on the menu issue. On the test boxes in virtualbox
that have only had R14 on them and have been updated since February with each
build, the menus and quicklaunch URLs are OK. The only box that got terribly
hosed was the actual non-virtual box that I removed my TDE 3.5.12 install and
replaced it with R14. That is the box that had the menus scattered and the
quicklaunch malformed URL problem.
Recall on the problem box, the 3.5.12 install was in /opt/kde3 and the profile
was ~/.kdemod3. All 3.5.12 packages were removed before installing R14, and the
ksyscoca in /var/tmp was removed. There was no migration script run, so the main
culprit appears to be handling of the menu files in ~/.config/menus and
/etc/xdg/menus. The new profile went in ~/.trinity, so the only issue I can see
is the old menu files.
I have not wiped the problem box yet to do another fresh R14 install. So let
me know if you want anything else off it. Also, let me know if you think the
/etc/xdg/menus files will cause issues on reinstall. I have deleted the
~/.config/menus files. Thanks.
--
David C. Rankin, J.D.,P.E.
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