X-Spam-Check-By: sourceware.org Message-ID: From: Kai Raphahn Subject: Re: Eliminating -mno-cygwin from gcc. X-Newsgroups: mls.cygwin.help User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit References: <45C76219 DOT 5010404 AT cwilson DOT fastmail DOT fm> <45C8E3C0 DOT 8010909 AT users DOT sourceforge DOT net> Date: Tue, 6 Feb 2007 22:30:25 +0100 To: cygwin AT cygwin DOT com X-Gate: Hamster/2.1.0.11 NewsToMail-Gate In-Reply-To: <45C8E3C0.8010909@users.sourceforge.net> Lines: 30 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 Frank Fesevur wrote: > At 5-2-2007 17:58, Charles Wilson wrote: >> Sounds to me like we need to consider extending the setup.ini format >> (and, by extension, the setup.hint format) to include an optional field: >> popup: This package is a significant change from the previous release. >> Please check the >> mailing list for the related announcement before continuing. > 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? Why not writing this Warning and future popups into a Logfile if --quit is set? Kai -- WCTYBTWHTKY We Could Tell You - But Then We'd Have To Kill You -- 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/