X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Matthew Woehlke Subject: Re: Eliminating -mno-cygwin from gcc. Date: Mon, 05 Feb 2007 10:06:41 -0600 Lines: 18 Message-ID: References: <020d01c748b4$62d8b170$2e08a8c0@CAM.ARTIMI.COM> <20070205030939.GB24653@trixie.casa.cgf.cx> <45C6A0DC.3010104@users.sourceforge.net> <20070205033101.GE24653@trixie.casa.cgf.cx> <45C6A793.8020008@users.sourceforge.net> <45C6ABAB.8030500@cygwin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061206 Thunderbird/1.5.0.9 Mnenhy/0.7.4.0 In-Reply-To: <45C6ABAB.8030500@cygwin.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Larry Hall (Cygwin) wrote: > The discussion has been to augment 'setup.exe' in a way as to provide users > with feedback about "important" package changes in general. It has come up > in the context of the gcc change but would have to apply generally. > "Important" would be defined by the maintainer by some mechanism. > Presumably, every release of package 'foo' does not trigger the "important" > flag. ;-) Hmm, there might be a catch-22 here. How do we force people to update their setup.exe? (What about a change that does not affect setup.exe itself? Maybe a package that most things depend on that allows a post-install script to display a dialog? Or was that the plan already?) -- Matthew This message is non-smoking -- 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/