Hi,
On 2023-05-25 13:05:57 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2023-05-25 09:09:45 -0400, Tom Lane wrote:
> >> Peter Eisentraut <peter@eisentraut.org> writes:
> >>> Why does pgindent require that pg_bsd_indent be installed in the path?
>
> > Isn't the situation actually *easier* in VPATH builds? There's no build
> > artifacts in the source tree, so you can just invoke the pg_bsd_indent built
> > in the build directory against the source tree, without any problems?
>
> Well, if you know where the build directory is, sure.
I'm imaginging adding make / meson targets 'indent-tree' and 'indent-head' or
such. Obviously the buildsystem knows where the source dir is, and you'd
invoke it in the build dir, so it'd know all that'd need to be known.
Attached is a prototype adding such meson targets. It's easier with a
parameter telling pgindent where the source tree is, so I addeded that too
(likely would need to be cleaned up some).
> Since pg_bsd_indent
> changes so seldom, keeping it in your PATH is at least as easy as any
> other solution, IMO.
>
> Another reason why I like to do it that way is that it supports running
> pgindent on files that aren't in the source tree at all, which suits
> some old habits of mine.
> But, as I said before, I'm open to adding support for other scenarios
> as long as we don't remove that one.
I can't imagine that we'd remove support for doing so...
Greetings,
Andres Freund