Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wyr3k-003fcX-32 for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Aug 2026 13:19:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wyr3i-0083QB-2D for pgsql-hackers@arkaria.postgresql.org; Tue, 25 Aug 2026 13:19:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wyr3i-0083Q1-1F for pgsql-hackers@lists.postgresql.org; Tue, 25 Aug 2026 13:19:22 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wyr3f-00000001BiO-3RWa for pgsql-hackers@lists.postgresql.org; Tue, 25 Aug 2026 13:19:21 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 67PDJ883618057; Tue, 25 Aug 2026 09:19:08 -0400 From: Tom Lane To: Andrew Dunstan cc: Greg Burd , PostgreSQL Hackers Subject: Re: Add a Nix flake In-reply-to: <58ed7628-7527-450d-8acc-b14a322e9375@dunslane.net> References: <58ed7628-7527-450d-8acc-b14a322e9375@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Tue, 25 Aug 2026 07:37:48 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <618055.1787663948.1@sss.pgh.pa.us> Date: Tue, 25 Aug 2026 09:19:08 -0400 Message-ID: <618056.1787663948@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > Historically we've been fairly resistant to carrying things related to > how people build or develop postgres. Yeah. I might hold my nose if the effects extended only to one more root-level file (although that's not great). But if we're talking about rather expansive .gitexclude patterns, I'm going to push back on the grounds of possible unforeseen side-effects on other peoples' work. regards, tom lane