Closed Bug 428571 Opened 17 years ago Closed 17 years ago

Installer of Firefox 2.0.0.13 installs into existing Firefox 3 beta 5 folder

Categories

(Firefox :: Installer, defect)

Product:
Firefox
Component:
Installer
Version:
2.0 Branch
Platform:
x86
Windows Vista
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: whimboo, Unassigned)

References

Details

If you install Firefox 2.0.0.13 onto a system which already has installed a beta version of Firefox 3 the latter one gets overwritten. It happens when you run the installer in standard or custom mode. Doing the standard way you will even not be warned. The final installation of Firefox 2.0.0.13 is not working due to bug 423226. The installer of Firefox 2.0.0.13 should use "Program Files\\Mozilla Firefox" as its default installation path. So official final releases will work in parallel with beta versions. IMO this behavior is a good example for bug 403883.
Flags: blocking1.8.1.15?
This is intentional with release builds when installing on a system with only a trunk build installed per Bug 361402. To change this would break automatically finding the last install location when installing a release build when a release build is already installed without adding complexity to the release installer to prevent this for people that install trunk builds. Resolving -> WONTFIX As a workaround you can run the installer, select custom, and choose a different install location when installing a release build on a system that only has a trunk build installed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Shouldn't only final release build install locations be detected? Can't we do that by changing non-release installers to not set the "install location" registry key (I'm assuming that we use a registry key for this)?
That would be the thing what I also expect and which is done the other way around? When you install a beta version of Firefox 3 it *doesn't* overwrite the already installed Firefox 2 version! So there is an inconsistency here. Users which installs a beta version want to test a software. This is not a final release. So the installer of older final releases shouldn't use such a beta version path to install the files into. Robert, IMO your decision is not correct to close this bug as Wontfix. But its your step now.
I have to add that the installer of Firefox 3 beta 5 overwrites each registry entry of Firefox 2.0.0.13. Users will not be able to uninstall Firefox 2 anymore after trying a beta version of Firefox 3. I don't really think that this is the desired behavior.
(In reply to comment #2) > Shouldn't only final release build install locations be detected? Can't we do > that by changing non-release installers to not set the "install location" > registry key (I'm assuming that we use a registry key for this)? There is no differentiation between the two currently and I'm not keen on doing this since the extra complexity would also affect release builds and not just nightly builds. (In reply to comment #4) > I have to add that the installer of Firefox 3 beta 5 overwrites each registry > entry of Firefox 2.0.0.13. Users will not be able to uninstall Firefox 2 > anymore after trying a beta version of Firefox 3. I don't really think that > this is the desired behavior. The uninstall entry in Add / Remove Programs should not be overwritten and it wasn't when I checked.
So why the installer of Firefox 2.0.0.13 uses the correct folder ("Mozilla Firefox") if a version of Firefox 2.0.0.x was already installed before the installation of beta 5? When I remove the 2.0.0.x version and restart the installer of Firefox 2.0.0.13 the beta 5 folder is used. Looks oddly to me.
(In reply to comment #5) > > I have to add that the installer of Firefox 3 beta 5 overwrites each registry > > entry of Firefox 2.0.0.13. Users will not be able to uninstall Firefox 2 > > anymore after trying a beta version of Firefox 3. I don't really think that > > this is the desired behavior. > The uninstall entry in Add / Remove Programs should not be overwritten and it > wasn't when I checked. Sorry, it should be the other way around. Installing Firefox 2 after the installation of Firefox 3 beta 5 the uninstaller entries for Firefox 3 beta 5 are overwritten. Only Firefox 2.0.0.13 is listed within the software list.
Because it installed into the same folder. When installing into the same directory all entries are overwritten and the uninstaller should (and does from my testing) remove all files including new files that the original uninstaller doesn't know about. At that point it wouldn't make sense to have two uninstall entries since you installed into the same directory... so only the last install is displayed. Is this not what you are seeing?
Flags: blocking1.8.1.15?
The clean-up is pretty fine but I hit this bug again today during the FF3.0.7 release testing and I lose my Firefox 3.1b3pre installation. It's cumbersome that you have to think about to choose the custom installation method when you wanna install an older build. :(
You need to log in before you can comment on or make changes to this bug.