Re: Upgrading KDE and it's dependencies
[Sorry to reply to my original posting, but I really thought that this
mail had not reached this mailing list - that's why I haven't watching
this thread. For some reason kmail still doesn't show my original mail
at all, although it exists in my Gmail inbox...]
My point below was aimed at upgrading KDE _without_ logging out
afterwards. It would be really nice to continue working even when KDE
has been upgraded in the background, especially with many sessions
open simultaneously. Any suggestions on avoiding the need to logout on
package level (like restarting kde daemons or something on upgrade)
and maybe also on KDE design level?
On 2005-06-19, Jarkko Suontausta wrote:
> Upgrading KDE when an older version is already running often causes a lot of
> trouble. This is mostly an upstream issue AFAIK, but it might be possible to
> add some preventive/corrective measures in the Debian packages. Does anyone
> have any ideas?