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

Hi,

On Wed, 7 Oct 2026 at 19:58, Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
>
> 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.

Thanks for the suggestion! I think this is worth trying because using
existing nls.mk files tremendously reduces the #lines_changed and also
removes the need of helper scripts.

> (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.)

Could you elaborate more on update-po? I didn't understand why running
it often would be a problem (I am also unsure if that is the case).

--
Regards,
Nazir Bilal Yavuz
Microsoft