X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20100726142944.GA28399@ednor.casa.cgf.cx> References: <30EAF1C130A74F97AC4C82B42ED55DAE AT hometoshiba> <20100725025446 DOT GA17000 AT ednor DOT casa DOT cgf DOT cx> <1179889566 DOT 20100726133244 AT mtu-net DOT ru> <20100726142944 DOT GA28399 AT ednor DOT casa DOT cgf DOT cx> Date: Mon, 26 Jul 2010 16:15:19 +0100 Message-ID: Subject: Re: Request for feature: more flexible setup routine From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 26 July 2010 15:29, Christopher Faylor wrote: > On Mon, Jul 26, 2010 at 12:52:48PM +0100, Andy Koppe wrote: >>#On 26 July 2010 10:32, Andrey Repin wrote: >>>> This makes me wonder whether Keep shouldn't be the default, on the >>>> principle that programs shouldn't do anything unless the user asks for >>>> it. >>> >>> Strange principle. >> >>It's the "Principle of Least Surprise". > > You can't argue that point if it would obviously surprise Andrey. =C2=A0It > would surprise me too given that it would be a profound departure from > previous behavior regardless of whether previous behavior was "right" or > "wrong". Yes, existing users always get shafted by UI changes (initially anyway), so it's short-term pain vs long-term gain. But in my ramblings I'd come down against changing the default from 'Curr' to 'Keep' anyway. > If we wanted to do something like this I think it would have to be a > separate dialog where the user makes a decision about what they want. > Either that or a list of packages to update would always be presented > so that people wouldn't be surprised. Agreed, but of course that'd need substantial design and implementation work, so realistically it isn't gonna happen. Okay, detour over. Now what about my actual proposal, which was to save the Keep/Curr/Prev/Exp setting across setup.exe invocations? Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple