On 2014-10-30 19:53:54 -0400, Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
> > On 2014-10-30 19:30:04 -0400, Tom Lane wrote:
> >> At some point down the road that value judgement might (hopefully will)
> >> reverse, and then we could deal with it by making --enable-tap-tests the
> >> default. But even then there would be a place for
> >> --disable-tap-tests.
>
> > Which would be what exactly?
>
> Well, for example, you don't have and don't want to install IPC::Run.
Well, that's what the hypothetical configure test is for. I see little
reason in this specific case to do anything more complicated than check
for prove and IPC::Run in configure and use them if necessary.
> Or you've tripped over some failure in the TAP tests (which might or
> might not be an actual bug) but would like to complete your build anyway.
Well. That's just the same with plain regression tests. But I guess
adding --disable is essentially free, so whatever.
Greetings,
Andres Freund
-- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services