[Sorry for the delay.] "Eric Y. Kow" <[EMAIL PROTECTED]> writes:
> Thanks for these (accepting all but one). Would #!/bin/sh --posix in > the harness help for making sure we don't use features we shouldn't? Unfortunately not. It would only (?) work if sh is bash and break otherwise. Setting POSIXLY_CORRECT in the environment also doesn't help since it doesn't suppress extensions. By the way, sh isn't bash on current Ubuntu; I'm not sure whether that's inherited from Debian or not. There are some rules about sh-ism in the GNU coding standards and the autoconf doc, but they probably don't cover the things I addressed. My non-trivial experience of this sort of thing is that you just have to test on relevant systems. If tests fail, you just have to debug it, though I suppose there's some risk of false successes. If you work to the intersection of POSIX and SysV, that should cover the vast majority of current systems. Perhaps the best general policy is not to write tests in sh if in doubt that the relevant features are supported, though some of us would rather not have to cope with perl... Anyway at least there are tests! >> Sun Feb 25 11:39:49 GMT 2007 Dave Love <[EMAIL PROTECTED]> >> * In tests, don't assume diff has -c, -x flags. > > You meant '-u, -x flags', right? Right. I'll resubmit. > I don't mean to be a pain for such a minor detail, but I'm thinking that > this might save us some future confusion. No problem -- well spotted. > By the way, are you still planning to resubmit the quoted matchers > stuff? Sorry, I'm not sure what that's about. _______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
