Re: Add pgindent test to check if codebase is correctly formatted - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Add pgindent test to check if codebase is correctly formatted
Date
Msg-id Zacu0ZfY-g95kSSU@momjian.us
Whole thread Raw
In response to Re: Add pgindent test to check if codebase is correctly formatted  ("Tristan Partin" <tristan@neon.tech>)
List pgsql-hackers
On Tue, Jan 16, 2024 at 07:32:47PM -0600, Tristan Partin wrote:
> It requires changes to at least the Meson build files. pg_bsd_indent is not
> marked for installation currently. There is a TODO there. pgindent has no
> install_data() for instance. pg_bsd_indent seemingly gets installed
> somewhere in autotools given the contents of its Makefile, but I didn't see
> anything in my install tree afterward.
> 
> Sure RPM/DEB packagers can solve this issue downstream, but that doesn't
> help those of that run "meson install" or "make install" upstream. Packagers
> are probably more likely to package the tools if they are marked for
> installation by upstream too.
> 
> Hope this helps to better explain what changes would be required within the
> Postgres source tree.

Yes, it does, thanks.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.



pgsql-hackers by date:

Previous
From: "Tristan Partin"
Date:
Subject: Re: Add pgindent test to check if codebase is correctly formatted
Next
From: David Rowley
Date:
Subject: Re: New Window Function: ROW_NUMBER_DESC() OVER() ?