X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <i0vpm6pur5ipemqekfb9m1467ggnbkr70v@4ax.com>
References: <ikf9e3$ub2$1 AT dough DOT gmane DOT org>	<ikfe1p$f00$1 AT dough DOT gmane DOT org>	<ikgf2f$vtm$1 AT dough DOT gmane DOT org>	<fggnm61cfbkp0fm6jm0lvrns74bk56bls4 AT 4ax DOT com>	<ikgjlh$tk7$1 AT dough DOT gmane DOT org>	<aamnm61uhbmgbrq007c6oag7cd7n9hpdt2 AT 4ax DOT com>	<ikgt6p$ubn$1 AT dough DOT gmane DOT org>	<4D6BFD09 DOT 8020600 AT gmx DOT de>	<AANLkTimi6R8MFSH63quHW3EqV4z5ucwtgNEPmCWWfjjc AT mail DOT gmail DOT com>	<4D6CD103 DOT 7000303 AT gmx DOT de>	<i0vpm6pur5ipemqekfb9m1467ggnbkr70v AT 4ax DOT com>
Date: Thu, 3 Mar 2011 06:56:03 +0000
Message-ID: <AANLkTi=XSNxNp1M5RBGdXqdVSFuE-3KvFnXN2Y1q1E2F@mail.gmail.com>
Subject: Re: setup.exe considerations (was: Doubtful about unison)
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 1 March 2011 14:04, Andrew Schulman wrote:
>> >> Which is the problem: the unison command was compiled against a newer
>> >> cygwin1.dll than yours.
>> >
>> > To be fair, setup.exe ought to be able to resolve or warn about such
>> > version dependencies. Unfortunately the infrastructure for that isn't
>> > in place, as it would require version requirements to be expressed in
>> > packages' setup.hint files (rather than in their READMEs, as they are
>> > at the moment).
>
> It would also require packagers to know what the version requirements are.
> I can record what versions of things were installed when I built Unison -
> or better yet, get cygport to record that for me - but I don't really know
> whether it would break with an earlier or later version of cygwin, etc.

I think it would be entirely reasonable to record the version you
built against as the minimum requirement, as you couldn't be expected
to test against older libraries as well. Wanting to use latest Unison
with an old Cygwin DLL is a case of having your cake and eating it,
it's just that it would be good if setup.exe was able to point that
out. But, in another bakery-related metaphor, this is pie-in-the-sky.

If Unison broke with a later Cygwin version, that would be a
compatibility bug that would need to be fixed asap anyway.

Andy

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