Message-ID: <49F58AE0.7070008@gmail.com>
Date: Mon, 27 Apr 2009 11:37:20 +0100
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com, config-patches@gnu.org
Subject: Re: Update config.guess to treat cygwin 1.7 as new system name
References: <49A77132.3060506@byu.net> <20090427064710.GA15625@air.net.au>
In-Reply-To: <20090427064710.GA15625@air.net.au>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Ben Elliston wrote:
> Hi Eric
> 
> On Thu, Feb 26, 2009 at 09:50:58PM -0700, Eric Blake wrote:
> 
>> The upcoming Cygwin 1.7.0 release adds so many APIs and improves so
>> much functionality that it probably deserves a separate designation
>> in config.guess.  For reference, notice the size of the most recent
>> beta announcement:
>> http://cygwin.com/ml/cygwin-announce/2009-02/msg00018.html
> 
> For consistency with other system triplets that append their version
> number, could we emit the version number unconditionally for all
> Cygwin systems? (eg. i686-pc-cygwin1.5)?

  Maybe I've missed something; if we do that, won't we have to audit every
configure script in the world looking for places that match "*-*-cygwin"
without a trailing wildcard?  Such scripts would need fixing before they'd
work with 1.7, true, but wouldn't it break a lot of things that currently work
just fine for 1.5?

    cheers,
      DaveK


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