| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: minimum perl version |
| Date: | 2022-09-14 03:46:12 |
| Message-ID: | 2505664.1663127172@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
John Naylor <john(dot)naylor(at)enterprisedb(dot)com> writes:
> On Wed, Sep 14, 2022 at 6:47 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I've just switched longfin to use built-from-source perl 5.14.0.
> In that case, here is a quick update with commit message. Not yet any
> change for MSVC, but I can put together something later.
Looks reasonable just by eyeball, did not test.
> Since we're much less willing to support older Windows and Visual
> Studio versions, maybe it's low-enough risk defer the check to the
> Meson conversion? I understand our MSVC process will then go away much
> more quickly than autoconf...
Agreed --- the MSVC scripts are on a pretty short leash now.
Not clear it's worth fixing them for this point. If we've
failed to get rid of them by the time v16 release approaches,
maybe it'd be worth doing something then.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-09-14 03:49:22 | Re: A small typo |
| Previous Message | Tom Lane | 2022-09-14 03:40:43 | Re: A small typo |