This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Doubtful about unison

On 1 March 2011 14:25, Olivier Lefevre wrote:
> On 3/1/2011 8:20 AM, Andy Koppe wrote:
>> To be fair, setup.exe ought to be able to resolve or warn about such
>> version dependencies.
> That's what I was tempted to say. For the record this is what I did:
> 1) select Keep
> 2) manually pick unison
> 3) accept the dialog about dependencies
> Yet AFAICT only Unison was installed.

Yeah, the Keep button should come with a at-your-own-risk warning really.

> This is complicated by the fact that I did not directly install but
> did a first download-without-installation and then installed from
> local bundles. The above is what happened at download time; I am no
> longer sure what I did at installation time but most likely the same.
> In a slightly different line of thought, isn't it rather brittle of
> Cygwin that a minor upgrade (I was already at some 1.7 version)
> breaks applications? Think, a contrario, of how you can still run
> ancient Windows apps on XP.

The problem you had was a case of broken forward compatibility,
whereas your Windows example is talking about backward compatibility.
The Cygwin devs do try hard to maintain the latter, so even really old
packages in the distribution continue to run with the latest DLL. What
isn't guaranteed to work is running packages built on the latest DLL
with an old DLL, because that's likely to depend on new features in
the latest DLL.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]