On Tue, 11 Nov 2014, Tor Arntsen wrote:

> What about other systems? libcurl builds and (mostly) tests on nearly 30
> differnt operating systems (lumping all Linux distros into one, and all
> Solaris versions into one - hardly fair, in the latter case). I for one
> prefer to be very conservative with respect to the build and test
> environment requirements, and only change when there is really no other
> option.

I completely agree with this. I have the deepest respect and gratitude to you
and other friends who provide builds and tests for older machines and
non-linux hosts and I know that without them we would bitrot a lot faster than
we otherwise do. In order to maintain an as wide as possible testing crowd, we
need to keep the environment as simple as possible with no "fancy stuff".

> I still want that Python change I mentioned reversed, so that more tests can
> run on more systems.

We have some python stuff in the test suite but it should not block anything
else if they can't run (and we should not push more tests into that python
world than we absolutely have to). If they do right now that's a mistake we
should rectify. What happens on these machines without python?

I allowed the python tests to get merged simply because our existing
pipelining tests are very limited and that test suite was so much better, so I
figured a test set that runs on a limited set of test machines would still be
better than not having these tests at all.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html