We don't have a mechanism to update existing Trinity profiles when updating to R14.
For the most part Trinity 3.5.11->3.5.13 profiles essentially are KDE3 profiles.
Although the r14-xdg-update script will run automatically for users the first time they
run the R14 starttde script, some profile breakage is likely to remain with older config
files because the r14-xdg-update script is limited in scope to XDG changes.
I suspect more than a few Trinity users are using 3.5.12 and we should ensure their R14
updating experience "just works."
1. How should we detect older profiles? Possibly by looking for the existence of
$TDEHOME/share/config twin_update, twinrc, or tdeprintrc? Any other reliable methods?
2. How should we help users update their profiles? Doing so transparently often is best.
Possibly the migratekde3 script can accommodate post 3.5.10 profiles although originally I
never considered anything other than 3.5.10.
Do any users have experience migrating existing profiles from 3.5.x to R14? What were
those experiences like?
Ideas? Thoughts?
Darrell
Show replies by date