> 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
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
On 3/1/2011 1:46 PM, Andy Koppe wrote:
Good idea, although that would entail unnecessary (and unwanted)
updates, for example, the Cygwin DLL would get updated whatever
package you installed, even if the package was built years ago.
Indeed and upgrading Cygwin itself is the very thing I was tryi
> >> 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 r
On 1 March 2011 10:57, Matthias Andree wrote:
> Am 01.03.2011 08:20, schrieb Andy Koppe:
>> On 28 February 2011 19:52, Matthias Andree 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 resol
Am 01.03.2011 08:20, schrieb Andy Koppe:
> On 28 February 2011 19:52, Matthias Andree 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. Unfortu
6 matches
Mail list logo
