Closed
Bug 836232
Opened 11 years ago
Closed 11 years ago
[stub installer] Use caching for the downloaded installer
Categories
(Firefox :: Installer, enhancement)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: whimboo, Unassigned)
References
Details
If you install Firefox through the stub installer and there is another running instance of Firefox (e.g. Nightly, Aurora) active, the installation will fail with the default settings. When you run the stub installer again it will re-download the whole package. Don't we have a cache we could make use of? Or is that not implemented yet?
Reporter | ||
Comment 1•11 years ago
|
||
So in the given case above Firefox has already been installed. So with my steps I triggered a completely new installation. So putting the downloaded file into the cache, would help to speed up installation time and lower the amount of data to download. Mostly people will be affected here, for whom the installation process failed.
Summary: [stub installer] If installation fails due to another running Firefox instance, the download is run again → [stub installer] Use caching for the downloaded installer
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Comment 3•11 years ago
|
||
Sounds like what you've described is the "resume support" enhancement in bug 798005.
Comment 4•11 years ago
|
||
Actually change that - this situation is a bit different as it's a cross-over in installs.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Reporter | ||
Comment 5•11 years ago
|
||
Right. Now sure what rob thinks about it but if we want to make use of a cache your resume bug would most likely depend on it.
Comment 6•11 years ago
|
||
Why did the install fail? The install typically succeeds even when Firefox is in use though we don't launch the new version as stated in the messagebox. The download performed by the stub does not use any existing profiles, caches, etc. and what it does use it cleans up at the end intentionally... it would be bad form to leave things like that around along with the goal is to successfully install the first time (which it does typically though there have been server side issues recently) so this would end up being for an edgecase.
Updated•11 years ago
|
Severity: normal → enhancement
Comment 7•11 years ago
|
||
As originally reported (In reply to Henrik Skupin (:whimboo) [away 03/15 - 03/22] from comment #0) > If you install Firefox through the stub installer and there is another > running instance of Firefox (e.g. Nightly, Aurora) active, the installation > will fail with the default settings. The installation hasn't failed for this case for quite some time. > When you run the stub installer again > it will re-download the whole package. > > Don't we have a cache we could make use of? Or is that not implemented yet? Per comment #6 we don't and intentionally don't keep these files around. Also, all stub installers download the latest build offered by bouncer for the channel associated with the stub so a cache as described could easily be problematic. Resolving -> wontfix
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•