Confirmed users
657
edits
| Line 8: | Line 8: | ||
: (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. | ||
: [[User:LawrenceMandel|LawrenceMandel]] Yes. Mobile is out of scope as updates are handled via a different process. (App store.) I hope that disk space (~75Mb on Mac) isn't an issue but I don't know. Could Firefox ever get into a state (say if a user has several updates to perform and doesn't reboot) where several updates have been installed and are hanging around on a system so that Firefox is eating up 300, 400, 500+ Mb of disk space at a time? | : [[User:LawrenceMandel|LawrenceMandel]] Yes. Mobile is out of scope as updates are handled via a different process. (App store.) I hope that disk space (~75Mb on Mac) isn't an issue but I don't know. Could Firefox ever get into a state (say if a user has several updates to perform and doesn't reboot) where several updates have been installed and are hanging around on a system so that Firefox is eating up 300, 400, 500+ Mb of disk space at a time? | ||
: (ehsan) Our system requirements page says that users need a minimum of 200MB of disk space, so I think we're safe there. The way that side-by-side approach is designed, you'll only ever have two directories: currentVersion and nextVersion. If a new version becomes available when there is already a nextVersion directory, we will just remove the old nextVersion directory and write a new one. | |||
=== Replacement approach === | === Replacement approach === | ||