X-Spam-Check-By: sourceware.org Message-ID: <3da3d8310702061246v5f5d02abo4d759b95987c9556@mail.gmail.com> Date: Tue, 6 Feb 2007 15:46:33 -0500 From: "Eliah Kagan" To: cygwin AT cygwin DOT com Subject: Re: Eliminating -mno-cygwin from gcc. In-Reply-To: <45C8E3C0.8010909@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <020d01c748b4$62d8b170$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <20070205030939 DOT GB24653 AT trixie DOT casa DOT cgf DOT cx> <45C6A0DC DOT 3010104 AT users DOT sourceforge DOT net> <20070205033101 DOT GE24653 AT trixie DOT casa DOT cgf DOT cx> <45C6A793 DOT 8020008 AT users DOT sourceforge DOT net> <45C6ABAB DOT 8030500 AT cygwin DOT com> <20070205162433 DOT GA9486 AT trixie DOT casa DOT cgf DOT cx> <45C76219 DOT 5010404 AT cwilson DOT fastmail DOT fm> <45C8E3C0 DOT 8010909 AT users DOT sourceforge DOT net> 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 2/6/07, Frank Fesevur wrote: > If you want a use a popup, please make it aware of the --quiet option! > > I run 'setup.exe --quiet' from a simple .bat script to update my > installation (first stopping and afterwards starting again my sshd). And > even that is not always free of popups (when files are still in use). > > Therefore I can't do a fully automatic update. And I know setup.exe is > not designed for unattended usages, but with the current command line > options it can act like it and I do use it that way. > > And could the 'file in use' message box also respect the --quiet option? > > Regards, > Frank Perhaps there could be a flag to cause setup.exe to succeed quietly in spite of such warnings (update the package anyway), and another to cause setup.exe to "gracefully degrade" quietly in the face of them (continue but skip updating the package and skip other updates with the updated version of the package as a dependency). One of these flags could be --quiet, or the current behavior of --quiet could be retained and two new flags such as --quietsucceed and --quietfail could be added. Then --quiet would continue to behave as people have learned it behaves. Perhaps it would even be useful to have different flags to set the answer to the question of whether or not to replace in-use files and to set the answer to the question of whether or not to upgrade packages when there is a "significant change." On the other hand, I suppose there is some question of whether or not additional structure should be added to the calling syntax of setup.exe until a silent mode is added whereby everything one can do in the interactive mode one can do in the silent mode (e.g. specifying packages and versions from the command line). -Eliah -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/