| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tristan Partin <tristan(at)neon(dot)tech> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Subject: | Re: Add pgindent test to check if codebase is correctly formatted |
| Date: | 2024-01-17 01:27:40 |
| Message-ID: | ZactDKLf8fk0YYsv@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 16, 2024 at 07:22:23PM -0600, Tristan Partin wrote:
> I think a good solution would be to distribute pgindent and pg_bsd_indent.
> At Neon, we are trying to format our extension code using pgindent. I am
> sure there are other extension authors out there too that format using
> pgindent. Distributing pg_bsd_indent and pgindent in the postgresql-devel
> package would be a great help to those of us that pgindent out of tree code.
> It would also have the added benefit of adding the tools to $PREFIX/bin,
> which would make the test that I added not need a hack to get the
> pg_bsd_indent executable.
So your point is that pg_bsd_indent and pgindent are in the source tree,
but not in any package distribution? Isn't that a packager decision?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tristan Partin | 2024-01-17 01:32:47 | Re: Add pgindent test to check if codebase is correctly formatted |
| Previous Message | Tristan Partin | 2024-01-17 01:22:23 | Add pgindent test to check if codebase is correctly formatted |