Re: Adding init-po and update-po targets to the meson build system

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Adding init-po and update-po targets to the meson build system
Date: 2026-10-07 16:58:31
Message-ID: CAOYmi+ngxO_k7BWbBPkdAqpckXoFF=GJCX8UWAHjxH5ojG35-Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 7, 2026 at 9:40 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
> Yes, I agree that it is kind of nightmarish. I considered both options
> and chose to use JSON files because, AFAIK, we want to remove the
> autoconf system and use meson in the future. So, using JSON files
> makes more sense to me from a maintainability perspective for this
> reason.

A third path might be to disentangle the NLS makefiles from
Makefile.global, so that you don't need Autoconf in order to make use
of their targets. Then the Meson targets could just defer to that
implementation.

(sslfiles.mk took a similar approach, and I've been happy with it so
far. The init-po use case seems somewhat close, at least, since a
developer doesn't need to run it very often. Not sure about
update-po.)

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Baji Shaik 2026-10-07 17:39:37 [PATCH] Unify duplicate-option handling across utility commands
Previous Message Fujii Masao 2026-10-07 16:46:33 Re: 041_checkpoint_at_promote.pl might fail due to race condition on child kill