Re: meson vs windows perl - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: meson vs windows perl
Date
Msg-id 8242c698-0dc8-4a4c-abec-e4d351b2ed65@dunslane.net
Whole thread Raw
In response to Re: meson vs windows perl  (Andrew Dunstan <andrew@dunslane.net>)
List 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




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Robocopy might be not robust enough for never-ending testing on Windows
Next
From: Tom Lane
Date:
Subject: Re: Mutable foreign key constraints