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-07-20 13:41:27
Message-ID: 3b415184-91d5-4649-a44a-b9d99817401e@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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.

cheers

andrew

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

Attachment Content-Type Size
ldopts4.patch text/x-patch 1.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2024-07-20 15:06:21 Re: Logical Replication of sequences
Previous Message Jelte Fennema-Nio 2024-07-20 12:09:30 Re: Report search_path value back to the client.