Re: [Evolution] new oaf problem ?

[Alec Peden <pezking jaded org>]

I dont want my desktop dying everytime i update my email client, nor
gnome-panel or any other app that will migrate to oaf. the best way to
do this is have Red Carpet tell you to reboot your machine. While this
is a big pain in the ass for me and probably many others, it seems to be
the best way around this for users that dont want to clean up old files.
My distro cleans up /tmp on startup, so this may account for me never
having the /tmp/orbit problem. i'm also hoping that after GNOME 1.4 is
released, API changes will only come with full version updates. 




On 06 Feb 2001 13:19:03 -0500, Michael Leone wrote:
> > its harmful because oaf-slay will kill any process using oafd. Right now
> > that isnt much but soon alot of other programs will be moving to it.
> > Alot of time i'll be in the middle of writing an email while Nautilus is
> > updating, now if the the rpm/deb's ran there oaf-slay scripts after it
> > was done installing, evolution would die (even tho i'm updating nautilus
> > and all my work would be lost. Once the APIs stablize, running oaf-slay
> > and rm old orbit files will be less frequent. rm'ing the t/mp/orbit*
> > files, while i havent had to do this and update nautilus/evolution
> > everyday, would have a similar effect on programs using ORBit.
>
> This presumes that you don't close any application that is using oaf before
> updating it. Or that there can't be an pre-install script that senses that
> oaf is currently in use (somehow), and tells you to exit all apps first.
>
> It's always good practice to close all apps before updating system-level
> components, such as oaf and ORBit.