public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Robert Haas <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Andrew Dunstan <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: meson oddities
Date: Wed, 04 Jan 2023 16:18:38 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+TgmoaO8Jxgn+gCTZf43jbnmpDRyGARd8LJnEC20n1SPNNgnQ@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CA+TgmoaO8Jxgn+gCTZf43jbnmpDRyGARd8LJnEC20n1SPNNgnQ@mail.gmail.com>
Robert Haas <[email protected]> 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
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: meson oddities
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox