Re: [BUG FIX]: invalid meson version detection

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Sergey Solovev <sergey(dot)soloviev(at)tantorlabs(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [BUG FIX]: invalid meson version detection
Date: 2024-08-19 07:09:38
Message-ID: a0fd8c52-6945-454a-b1d6-9d7353544f27@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14/08/2024 17:02, Sergey Solovev wrote:
> I looked at meson.build file at found an incorrectly used function to
>
> determine postgres version.
>
>
> > if pg_version.endswith('devel')
> >   pg_version_arr = [pg_version.split('devel')[0], '0']
>
>
> There should be `pg_version.contains('devel')`, not `endswith`. Like this:
>
> -if pg_version.endswith('devel')
> +if pg_version.contains('devel')

I believe it's correct as it is. With "beta" and "rc" version, the
version strings look like "17beta1" or "16rc2", i.e. there's a number at
the end of the string. But the "devel" version strings never have that,
e.g. "17devel" or "18devel".

See also src/tools/version_stamp.pl

--
Heikki Linnakangas
Neon (https://neon.tech)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2024-08-19 07:10:27 Re: Pgoutput not capturing the generated columns
Previous Message shveta malik 2024-08-19 07:03:04 Re: Conflict detection and logging in logical replication