From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: meson and sslfiles.mk in src/test/ssl/ |
Date: | 2023-02-22 13:40:41 |
Message-ID: | 3e87008f-caa3-9268-7cca-30e34ec6e59e@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 21.02.23 00:54, Michael Paquier wrote:
> While playing with the SSL tests last week, I have noticed that we
> don't have a way to regenerate the SSL files with meson for its TAP
> suite. It seems to me that we had better transfer the rules currently
> stored in sslfiles.mk into something that meson can use?
>
> Another approach may be to keep sslfiles.mk around, still allow meson
> to invoke it with a specific target? I am not exactly sure how this
> would be handled, but it looks like a transfer would make sense in the
> long-term if we target a removal of the dependency with make.
I think the tradeoff here is, given how rarely those rules are used, is
it worth maintaining duplicate implementations or complicated bridging?
It's clearly something to deal with eventually, but it's not high priority.
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2023-02-22 13:46:50 | Re: Missing cases from SPI_result_code_string() |
Previous Message | Daniel Gustafsson | 2023-02-22 13:39:23 | Re: Raising the SCRAM iteration count |