On Sun, Mar 29, 2009 at 1:02 PM, Thomas Van Lenten <[email protected]> wrote: > Most mac apps solve this by having the app exit as part of the upgrade > process, this way a new copy is launched w/ the new resources.
yes, but this is the problem with silent autoupdate. We don't want to force the user to stop what they're doing when an update starts. Erik > On Sun, Mar 29, 2009 at 4:40 AM, John Grabowski <[email protected]> wrote: >>> >>> How will in-place updating work on the Mac and Linux? >> >> To be frank, we haven't solved this problem on Mac. >> Right now we're doing an rsync to klobber on update, which is fine for >> pre-dogfood. E.g. our "normal" Mac crash rate far exceeds any possible >> crashes caused by version mismatching in the 3 auto-updates we have sent out >> internally. >> Although we could load all resources on startup, that ignores one critical >> piece. Since renderers are separate processes and are launched on-demand, >> we would still have the problem of "old browser" talking to "new renderer". > > All platforms would have this problem if they don't force the apps to bounce > as part of the upgrade process, no? > TVL > >> >> I suspect we'll need to have either a versioned scheme line Windows, or a >> "complete upgrade" step on initial launch. >> jrg >> >> >> >> >> >> > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
