Re: how to handle missing "prove"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: how to handle missing "prove"
Date: 2014-11-02 16:36:21
Message-ID: 32590.1414946181@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On 10/30/14 9:09 PM, Tom Lane wrote:
>> Looks generally reasonable, but I thought you were planning to choose a
>> different option name?

> Yeah, but I couldn't think of a better one. (Anything involving,
> "enable-perl-..." would have been confusing with regard to PL/Perl.)

Committed patch looks good, but should we also add the stanza we discussed
in Makefile.global.in concerning defining $(prove) in terms of "missing"
if we didn't find it? I think the behavior of HEAD when you ask for
--enable-tap-tests but don't have "prove" might be less than ideal.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-11-02 16:53:52 Re: Let's drop two obsolete features which are bear-traps for novices
Previous Message Tom Lane 2014-11-02 16:28:39 Re: How to implent CONVERT ( data_type [ ( length ) ] , expression ) function in postgreSQL