Re: Test::More version - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Test::More version
Date
Msg-id 1613101.1636663467@sss.pgh.pa.us
Whole thread Raw
In response to Re: Test::More version  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Test::More version
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2021-Nov-11, Andrew Dunstan wrote:
>> Perhaps we could add a line to one of the TAP tests that would spit out
>> the version on the log?

> Maybe have it spit out the version of *all* the modules we require
> (which aren't all that many), not just Test::More?

Yeah ... configure is already checking those versions, so maybe we could
make it print them out along the way?  I'd been thinking of doing exactly
this just for documentation purposes, so if there's a concrete need for
it, let's get it done.

Having said that, I don't think I believe that changelog entry,
because prairiedog is doing just fine with

$ perl -MTest::More -e 'print "$Test::More::VERSION\n"'
0.8701

I have no objection to updating prairiedog to whatever new minimum
version we settle on.  But if there are other buildfarm animals with
old versions, that might be a reason not to change it.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] postgres_fdw: suppress explicit casts in text:text comparisons (was: column option to override foreign types)
Next
From: Isaac Morland
Date:
Subject: Re: Should AT TIME ZONE be volatile?