X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-5.4 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_BG
X-Spam-Check-By: sourceware.org
X-Received: by 10.50.108.235 with SMTP id hn11mr5315574igb.107.1362477250720;        Tue, 05 Mar 2013 01:54:10 -0800 (PST)
Date: Tue, 5 Mar 2013 03:54:06 -0600
From: Yaakov (Cygwin/X) <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Shouldn't gcc-4 depend on libmpfr4 ?
Message-ID: <20130305035406.795fc5cd@YAAKOV04>
In-Reply-To: <loom.20130305T101428-417@post.gmane.org>
References: <CAEhDDbDwsH=CvsJXFFTgbrEhVp_-sUU-q-=tJONYaKP=m95Weg@mail.gmail.com>	<5131CD7E.8050001@gmail.com>	<loom.20130304T080048-222@post.gmane.org>	<20130304090904.GA5468@calimero.vinschen.de>	<loom.20130304T110538-61@post.gmane.org>	<20130304161925.GA4078@calimero.vinschen.de>	<loom.20130304T193416-681@post.gmane.org>	<CA+sc5mk2MgnjYA2OtaK7d7Aed_tpqXVoD=80NVQ6-uO=LNSUpw@mail.gmail.com>	<87ip57nf3r.fsf@Rainer.invalid>	<loom.20130305T101428-417@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Tue, 5 Mar 2013 09:18:04 +0000 (UTC), Achim Gratz wrote:
> The remaining problem is that the library version changes from
> cyggmp-3 to cyggmp-10.  Not sure how to deal with that or if the new
> package should just be libgmp10 instead of libgmp3 (I have the same
> problem with mpc, the old way of forcing the version doesn't work there
> anymore).

As packagers, we shouldn't be messing around with DLL version numbers
unless a mistake has clearly been made and confirmed upstream.  Correct
version bumps means ABI incompatibilities, so you can't just force back
the version without breaking existing software already built against
the old version.


Yaakov


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

