Re: contribcheck and modulescheck of MSVC's vcregress.pl cannot work independently - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: contribcheck and modulescheck of MSVC's vcregress.pl cannot work independently
Date
Msg-id CAB7nPqRzWTE5fz=HbcQ56sHvLeXmk7Pa8=L7uzevPfLsjvHCkg@mail.gmail.com
Whole thread Raw
In response to Re: contribcheck and modulescheck of MSVC's vcregress.pl cannot work independently  (Noah Misch <noah@leadboat.com>)
Responses Re: contribcheck and modulescheck of MSVC's vcregress.pl cannot work independently  (Noah Misch <noah@leadboat.com>)
List pgsql-bugs
On Mon, Jul 6, 2015 at 10:04 PM, Noah Misch wrote:
>> Also, if we would
>> want to have a real installcheck mode, what we should use is not the
>> path to what has been built but the path to the installation that the
>> Postgres instance needed is using. Now if you want to fix it if you
>> fix that's incorrect I won't complain about that :)
>
> I don't wish to.  I was content with released-branch vcregress.pl semantics.

Attached is a patch to revert to the pre-9.4 way of doing... If MSVC
should imitate what make does, perhaps you have an opinion about the
ideas I sent upthead to add a check-mode to contribcheck and
modulescheck? That's 9.6 work.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PQexec() hangs on OOM
Next
From: sshang@pivotal.io
Date:
Subject: BUG #13489: pg_attribute.attndims turns to 0 when 'create table like/as'