| |||||||||||||
Day: GNOME OSDay: GNOME OSPosted Aug 9, 2012 8:39 UTC (Thu) by krake (subscriber, #55996)In reply to: Day: GNOME OS by endecotp Parent article: Day: GNOME OS
"I don't know how it works on the Mac, where presumably the app being upgraded might still have windows visible. My guess is that it is killed with some notice first."
I wouldn't be so sure. The blog indicated that Chrome wants to be running during and after the upgrade and it said Linux makes that difficult and Windows and OS X don't.
Therefore we msut assume that the Mac store update process allows applications to continue to run. There is just no confirmation on that yet and not details how it does it.
(Log in to post comments)
Day: GNOME OS Posted Aug 9, 2012 9:30 UTC (Thu) by hummassa (subscriber, #307) [Link]
this is probably because the Mac upgrade process changes the whole /Applications/Google\ Chrome directory and the old application + the old shared objects is running from the old directory, so you don't have the problem you usually have *during* an apt-get dist-upgrade that if your running applications dlopen(), they do that with the *new* libraries (possibly inconsistently with what they are expecting).
|
|||||||||||||