delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2007/02/05/11:25:10

X-Spam-Check-By: sourceware.org
Date: Mon, 5 Feb 2007 11:24:33 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Eliminating -mno-cygwin from gcc.
Message-ID: <20070205162433.GA9486@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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> <eq7kmh$f85$2 AT sea DOT gmane DOT org>
Mime-Version: 1.0
In-Reply-To: <eq7kmh$f85$2@sea.gmane.org>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Mon, Feb 05, 2007 at 10:06:41AM -0600, Matthew Woehlke wrote:
>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?

Doesn't setup.exe warns if the setup.ini being used has a different
version number?

In any event, we are, of course, going to send out details in
cygwin-announce.

>(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?)

I suppose that you could add a post-install script but it is too late at
that point.  This would force a normal cygwin user into a reinstall frenzy
from which they might not ever recover.  It might be better than nothing,
though.

cgf

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019