168239 - [RFE]Custom Install over previous installation shouldn't default to installing everything.

Status: RESOLVED DUPLICATE of bug 92357

(SeaMonkey :: Installer, enhancement)

Description

[Jason Bassford]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020912
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020912

When installing a nightly on top of an existing install, all of the component
boxes are checked.  However, since the installer is smart enough to know what
you've already installed (and prevent you from checking/unchecking those boxes)
it should also "know" that the components you installed last time are most
likely the only components you want to install this time.

Speaking personally, I only install the browser, PSM, and Chatzilla.  So every
time I install a new nightly I end up having to uncheck 5 of the boxes.  It gets
a bit tiring.

I understand that everything should be checked (even in a Custom Install) if
there is no previous installation - we want to encourage people to try out all
of the components for testing purposes.  But if a previous version *does* exist
the choices made then should be taken as an explicit decision as to what the
user wants to use...

(I searched Bugzilla for something like that that was currently open or might
have been marked WONTFIX but was unable to come up with it.  Strange, since I
would have thought somebody else would have brought this up by now.  I'll leave
this bug UNCONFIRMED for now since something still tells me I might have missed
it and this could be a dupe.)

Reproducible: Always

Steps to Reproduce:

Comment 1

[Grace Bush]

confirming and marking as enhancement-currently it is working as designed.

Comment 2

[Jason Bassford]

Why is PSM no longer selected and grayed out in the more recent builds?  If the
installer is to intelligently select only those components previously installed
(this bug) why has the PSM component reverted to a not-previously installed
state?  (By "previously installed" I mean a component that is selected and
grayed, such that it cannot be unselected.)

Comment 3

[Diana Osborn]

So if a componet was installed in a prior installation and a clean install is
not selected, then the componet will not be unselectable?  All the components
were checked but greyed out when I did this install (over the last version that
was on this machine (Win XP) Mozilla 1.3b).

Comment 4

[Jason Bassford]

Er, no.

The intent of this bug is that ONLY previously installed components should be
checked.  (Currently, everything is checked, whether or not you installed it
previously.) Anything that you did NOT have installed previously, should NOT be
selected by default if you pick a custom install.  You can always check them
yourself - but the assumption should be that if you didn't install a component
previously you won't want to install it this time.

In terms of previously installed components, they should come up as checked by
default.  Assuming that the installer has the ability to *remove* an already
installed component (and I don't think it does yet - I'm fairly sure that
there's another bug open on that issue) then you should be able to uncheck it.

Comment 5

[R.K.Aa.]

*** Bug 247384 has been marked as a duplicate of this bug. ***

Comment 6

[Andrew Schultz]

*** Bug 190973 has been marked as a duplicate of this bug. ***

Comment 7

[Mel Reyes]

Addditionally, combining and removing some installer pages would be great.  For
example currently with the Firefox install the following can be done:
- Remove the "Setup Type" screen
- Combine the "Install Folder" and "Select Components" screens into one,
possibly even Setup Shortcuts if it will fit.

The key thing here is that for a "Custom" install there are too many screens and
it should either remember that it was a custom install and the previously
installed components or just have them all on one page and make them the
default.  Possible even an installer much like the Moden UI from Nullsoft
Installer, with a dropdown for Standard, Custom, etc.

The installer for Mozilla drives me even crazier with it not remembering Quick
Launch and having one option per screen.

I sure do hope some progress could be made with the installers and the Firefox
1.0 experience should be 2-3 clicks to install and 2-3 clicks to install
upgrades, etc.  Thanks again folks, MOZILLA ROCKS!!!!

Comment 8

[Boris 'pi' Piwinger]

There is actually an older bug covering this and explaining some workaround.

pi