| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me> |
| Subject: | Re: Preliminary results for proposed new pgindent implementation |
| Date: | 2017-05-19 16:31:14 |
| Message-ID: | 1755.1495211474@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, May 19, 2017 at 11:22 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I certainly would rather that our version matched something that's under
>> active maintenance someplace. But it seems like there are two good
>> arguments for having a copy in our tree:
>>
>> * easy accessibility for PG developers
>>
>> * at any given time we need to be using a specific "blessed" version,
>> so that all developers can get equivalent results. There's pretty much
>> no chance of that happening if we depend on distro-provided packages,
>> even if those share a common upstream.
> Yeah, but those advantages could also be gained by putting the
> pgindent tree on git.postgresql.org in a separate repository. Having
> it in the same repository as the actual PostgreSQL code is not
> required nor, in my opinion, particularly desirable.
It adds an extra step to what a developer has to do to get pgindent
up and running, so it doesn't seem to me like it's helping the goal
of reducing the setup overhead.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-05-19 16:38:13 | Re: Preliminary results for proposed new pgindent implementation |
| Previous Message | Andres Freund | 2017-05-19 16:30:08 | Re: Preliminary results for proposed new pgindent implementation |