Re: meson oddities - Mailing list pgsql-hackers

From Tom Lane
Subject Re: meson oddities
Date
Msg-id 2339907.1672867118@sss.pgh.pa.us
Whole thread Raw
In response to Re: meson oddities  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: meson oddities
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> If we don't do as Peter suggests, then any difference between the
> results of one build system and the other could either be a bug or an
> intentional deviation. There will be no easy way to know which it is.
> And if or when people switch build systems, stuff will be randomly
> different, and they won't understand why.

> I hear your point too. It's unpleasant for you to spend a lot of
> effort overriding meson's behavior if the result is arguably worse
> than the default, and it has the effect of carrying forward in
> perpetuity hacks that may not have been a good idea in the first
> place, or may not be a good idea any more. Those seem like valid
> concerns, too.

Yeah.  I think the way forward probably needs to be to decide that
we are (or are not) going to make changes to the installation tree
layout, and then make both build systems conform to that.  I don't
really buy the argument that it's okay to let them install different
layouts.  I *am* prepared to listen to arguments that "this is dumb
and we shouldn't do it anymore".

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Getting an error if we provide --enable-tap-tests switch on SLES 12
Next
From: Andrew Dunstan
Date:
Subject: Re: verbose mode for pg_input_error_message?