Re: [Libusb-devel] cygwin errors with latest libusb-stuge

[Segher B. <se...@ke...>]

> If 9 months is what we want to affix with the label "obsolete", that's
> not going to fly.

Nine months old autoconf, agreed.  Nine months old cygwin?  I have no
idea how old their tools are, if it's anything like OSX it's not good :-)

> To me obsolete should not apply to anything that's
> less than 2 years, because I fully expect people to use 2 year old
> development platforms, especially on Windows.

Two years is a bit long, but for most problems I would aim for around
that yes.

Also, note that it really isn't hard at all to install a newer autotools
(from source) when you need it.

>> The required version here
>> would be two years old (if I understand correctly), an eternity!
>
> Nope. Found that my 1 year old autoconf 2.65 version (src released
> 2009.11) wouldn't work either,

Huh strange, so it's another bug than what Peter dug up.

> Do you upgrade your autotools every 6 months?

More often than that, but sure, that's not what you meant :-)


Segher