Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dBkpj-0004QP-CO for pgsql-hackers@arkaria.postgresql.org; Fri, 19 May 2017 16:32:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dBkpi-0001UT-Vd for pgsql-hackers@arkaria.postgresql.org; Fri, 19 May 2017 16:32:55 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dBkoC-0006FU-LC for pgsql-hackers@postgresql.org; Fri, 19 May 2017 16:31:20 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dBko9-000262-4g for pgsql-hackers@postgresql.org; Fri, 19 May 2017 16:31:19 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v4JGVEGo001756; Fri, 19 May 2017 12:31:14 -0400 From: Tom Lane To: Robert Haas cc: Stephen Frost , "pgsql-hackers@postgresql.org" , Piotr Stefaniak Subject: Re: Preliminary results for proposed new pgindent implementation In-reply-to: References: <30527.1495162840@sss.pgh.pa.us> <26654.1495203668@sss.pgh.pa.us> <20170519150526.GX3151@tamriel.snowman.net> <29626.1495207374@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Fri, 19 May 2017 12:21:52 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1754.1495211474.1@sss.pgh.pa.us> Date: Fri, 19 May 2017 12:31:14 -0400 Message-ID: <1755.1495211474@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Robert Haas writes: > On Fri, May 19, 2017 at 11:22 AM, Tom Lane 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers