Re: meson vs windows perl

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Muralikrishna Bandaru <muralikrishna(dot)bandaru(at)enterprisedb(dot)com>, Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>
Subject: Re: meson vs windows perl
Date: 2024-09-14 14:39:11
Message-ID: 8242c698-0dc8-4a4c-abec-e4d351b2ed65@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2024-07-30 Tu 3:47 PM, Andrew Dunstan wrote:
>
> On 2024-07-20 Sa 9:41 AM, Andrew Dunstan wrote:
>>
>> On 2024-05-28 Tu 6:13 PM, Andres Freund wrote:
>>> Hi,
>>>
>>> On 2024-04-05 16:12:12 -0400, Andrew Dunstan wrote:
>>>> OK, this has been fixed and checked. The attached is what I propose.
>>> The perl command is pretty hard to read. What about using python's
>>> shlex
>>> module instead? Rough draft attached.  Still not very pretty, but
>>> seems easier
>>> to read?
>>>
>>> It'd be even better if we could just get perl to print out the flags
>>> in an
>>> easier to parse way, but I couldn't immediately see a way.
>>>
>>>
>>
>> Thanks for looking.
>>
>> The attached should be easier to read. The perl package similar to
>> shlex is Text::ParseWords, which is already a requirement.
>
>
> It turns out that shellwords eats backslashes, so we would need
> something like this version, which I have tested on Windows. I will
> probably commit this in the next few days unless there's an objection.
>

pushed

cheers

andrew

--

Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-09-14 14:51:49 Re: Mutable foreign key constraints
Previous Message Andrew Dunstan 2024-09-14 14:22:11 Re: Robocopy might be not robust enough for never-ending testing on Windows