On Friday 31 August 2012 07:24:41 Sune Vuorela wrote: > On 2012-08-30, David Faure <fa...@kde.org> wrote: > > I think this is a "belt and suspenders" kind of thing (extra > > precaution)... in theory it's not necessary, kded will detect new desktop > > files on kde startup, or during the upgrade process if KDE is already > > running. > > > > I wonder if Waldo added that (long ago) for the case where we change > > fields in ksycoca and forget to increase the version number while doing > > so. > > It is, though, highly annoying when the number is changed as, if I > understand things correctly, it requires a relogin and restart of > everything immediately after upgrade (and not when it fits your workflow > a bit later) in order to keep applications that loads plugins or uses > kio working
I seriously doubt that. The next app which uses ksycoca will rebuild it with the new version. I think you're confusing this with "new symbols in kdelibs". *That* is what forces you to logout/login or run kdeinit4 in a terminal. This is due to the fork-and-load-module behavior of kdeinit4. Updating kdelibs breaks that, apps expect symbols that the old kdeinit4 doesn't provide. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5
