Evan Layton wrote: > On Jun 19, 2009, at 11:11 PM, Shawn Walker <swalker at opensolaris.org> wrote: > >> On Jun 19, 2009, at 4:16 PM, Evan Layton wrote: >>> Danek Duvall wrote: >>>> On Thu, Jun 18, 2009 at 10:36:59AM -0600, Evan Layton wrote: >>>>> (http://opensolaris.org/os/project/caiman/CVERS/CVERS-FUNC/) >>>> I think if you're going to allow the install to move forward after a >>>> mismatch, it really needs to be opt-in, not opt-out. Don't make it >>>> easy >>>> for the customer to screw their system up. Ultimately, I think the >>>> spec >>>> needs a solid justification as to why the install should be allowed to >>>> proceed after a mismatch is discovered. It sounded like you had a >>>> developer ease-of-use argument, but I don't see that here. We had also >>>> talked about limiting continuation to the situation where you are >>>> booted >>>> from an older version than you're trying to install. >>> >>> We want to continue the installation if at all possible since the >>> user has asked for an installation. Most of the time this will be an >>> automated install and the user will not be expecting to have to do >>> interaction to complete an installation. Therefore we will continue >>> the installation in this case and the user will be warned and the >>> error or warning will be logged. >> >> Yes, the user requested an install, but there is possibly significant >> risk involved due to the mismatch. Do we really want an automated >> possibly broken install? >> >> Cheers, >> -- >> Shawn Walker > > > This was discussed at legth with Frank and yes we want to give the error > and warning to the user that they are attempting an unsupported install. > At that point we continue with the install and make a "best" effort to > complete the install. Most of the time this will be fine as the the > differences will tend to be minor. > > -evan
I should also mention that it is not expected that this will be a common occurrence but is sothing that would be mostly caused by a mis-configured install manifest. -evan
