Re: Adding init-po and update-po targets to the meson build system - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Adding init-po and update-po targets to the meson build system
Date
Msg-id CAOYmi+=2BYP-rZis9Q2SuayDas1E4CML-KUixoBbDTNmY6Tibw@mail.gmail.com
Whole thread
In response to Re: Adding init-po and update-po targets to the meson build system  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
List pgsql-hackers
On Thu, Oct 8, 2026 at 4:01 AM Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> After thinking more about that, I am not sure if that is an acceptable
> solution. In the Postgres docs [1] we mention that 'GNU make' is not
> needed when Postgres is built with meson and I think we don't want to
> break this promise.

I don't think it should be required for someone to run the build
itself. But realistically, saying "hey to perform this one-off
generation task as a contributor, you need GNU make as well" is not a
step backwards.

> Perhaps this is acceptable because the current
> case is specific and not widely used.

Right. That's what I was alluding to when I said I wasn't sure about
update-po -- I couldn't remember whether it was tangled into any of
the other build logic. I don't think it is, though.

> Also, I realized that there is no way to regenerate SSL files like
> sslfiles.mk does :(.

I don't think anyone has asked yet. It'd be a SMOP to have Meson
invoke the Makefile for you... but running Make manually when a new
certificate is sporadically added is a pretty small cost already.

Just my two cents.

Thanks,
--Jacob



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: serializable anomaly - duplicate primary keys
Next
From: "ZizhuanLiu X-MAN"
Date:
Subject: Re: Optimize MCV stats for sortable types and utilize sorted-order properties