Confirmed users
2,473
edits
| Line 4: | Line 4: | ||
This is the approach where Firefox would download an update in the background, apply and install it alongside with the existing installation, and would then wait for the next startup. At startup, the firefox.exe stub would look for the existing installation directories, and would pick the newest one, and start up either by loading xul.dll and the rest of the libraries from that directory or by running a firefox.exe from that directory. After startup, when the next update arrives, the older version (which is not in use any more) will first be removed, then the new update will be applied and it will get picked the next time that Firefox starts up.<br> | This is the approach where Firefox would download an update in the background, apply and install it alongside with the existing installation, and would then wait for the next startup. At startup, the firefox.exe stub would look for the existing installation directories, and would pick the newest one, and start up either by loading xul.dll and the rest of the libraries from that directory or by running a firefox.exe from that directory. After startup, when the next update arrives, the older version (which is not in use any more) will first be removed, then the new update will be applied and it will get picked the next time that Firefox starts up.<br> | ||
---- | |||
: [[User:LawrenceMandel|LawrenceMandel]] The way I read this there will be two copies of Firefox on the system during an update: the currently running Firefox and a completely new, updated Firefox. Is this correct? Will this require twice the disk space? How much disk space are we talking about? Is this a concern? | : [[User:LawrenceMandel|LawrenceMandel]] The way I read this there will be two copies of Firefox on the system during an update: the currently running Firefox and a completely new, updated Firefox. Is this correct? Will this require twice the disk space? How much disk space are we talking about? Is this a concern? | ||
: (ehsan) Yes, we're talking about having two copies of Firefox on a system. This would require twice the amount of disk space (although we could resort to hardlinking on platforms which support it to reduce this). It would be an issue for mobile, except that mobile is completely out of scope here. I'm not sure if this is a concern with Desktop Firefox. | : (ehsan) Yes, we're talking about having two copies of Firefox on a system. This would require twice the amount of disk space (although we could resort to hardlinking on platforms which support it to reduce this). It would be an issue for mobile, except that mobile is completely out of scope here. I'm not sure if this is a concern with Desktop Firefox. | ||