| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: how to handle missing "prove" |
| Date: | 2014-10-31 00:11:35 |
| Message-ID: | 5452D3B7.1040603@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/28/14 10:01 PM, Peter Eisentraut wrote:
> On 10/28/14 9:16 PM, Tom Lane wrote:
>> ISTM that the project policy for external components like this has been
>> "don't rely on them unless user says to use them, in which case fail if
>> they aren't present". So perhaps what we ought to have is a configure
>> switch along the lines of "--enable-tap-tests". If you don't specify it,
>> prove_check expands to nothing. If you do specify it, we fail if we
>> lack any of the expected support, both "prove" and whatever the agreed-on
>> set of Perl modules is.
>
> That's also a good idea.
Here is a patch.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Add-configure-enable-tap-tests-option.patch | text/x-diff | 5.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-10-31 00:13:53 | Re: TAP test breakage on MacOS X |
| Previous Message | Andres Freund | 2014-10-31 00:07:21 | Re: TAP test breakage on MacOS X |