Karl Fogel <kfogel@galois.ch.collab.net> writes:
> So moving from our current Bourne script to either Perl or Python is
> already a step up in portability.
Agree. "The set of tools guaranteed to exist on any Unix OS" is not a
sufficient yardstick for measuring portability of our test suite.
Our client runs on every platform that APR does, which includes BeOS
and Win32.
> > I'd say we're fine to output a nice message saying "you need at
> > least version X of language Y to run the test suite" instead. We
> > could have a warning displayed in the configure script.
>
> +1 on that.
+1.
The people who run `make check` will always be a smaller group than
those who run `make && make install`. I think it's great that the
latter group will never need any tools beyond cc and sh; that's the
biggest and more important group. Adding an extra language
requirement for the smaller group, however, is very small price to pay
in return for protecting test-writers' sanity. :)
Received on Sat Oct 21 14:36:25 2006