On Wed, May 27, 2009 at 7:11 AM, Dan Kegel <[email protected]> wrote: > The problem with that, and with the hard link, is that the > package manager cleans up the old version > when the update happens, so it's no longer available > to run. (And if we tried to keep them around, we'd > have a garbage collection problem.) It just doesn't > fit well, the package managers have no concept of > "leave these files installed until this process exits" > or "leave these files installed until the n+1th update".
Also, there are issues with shared libraries that we need. An upgrade may bring in a new major version of libxyz and update chromium to match at the same time, but our versioned hardlink is still going to need the old one. What we really want are transient references to the binary and it's shared libraries which we can get by just holding file descriptors to them. However, we would then have to write a userspace fexecve function to build a new child from the references. I think that could actually be done, but it's not going to be nice code :) AGL --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
