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 1wz6Ro-003oUC-0P for pgsql-hackers@arkaria.postgresql.org; Wed, 26 Aug 2026 05:45:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wz6Rm-00BNcE-2g for pgsql-hackers@arkaria.postgresql.org; Wed, 26 Aug 2026 05:45:14 +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 1wz6Rm-00BNc5-1j for pgsql-hackers@lists.postgresql.org; Wed, 26 Aug 2026 05:45:14 +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 1wz6Rk-00000001JAr-0MIS for pgsql-hackers@lists.postgresql.org; Wed, 26 Aug 2026 05:45:14 +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 67Q5j1F2668928; Wed, 26 Aug 2026 01:45:01 -0400 From: Tom Lane To: "Greg Burd" cc: "Andrew Dunstan" , "PostgreSQL Hackers" Subject: Re: Add a Nix flake In-reply-to: References: <58ed7628-7527-450d-8acc-b14a322e9375@dunslane.net> <618056.1787663948@sss.pgh.pa.us> Comments: In-reply-to "Greg Burd" message dated "Wed, 26 Aug 2026 01:33:18 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <668926.1787723101.1@sss.pgh.pa.us> Date: Wed, 26 Aug 2026 01:45:01 -0400 Message-ID: <668927.1787723101@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Greg Burd" writes: > On Tue Aug 25, 2026 at 6:37 AM CDT, Andrew Dunstan wrote: >> Well, "growing" could cover a multitude of possibilities. It could mean >> there was one and now there are two. [...] But if you want to say that >> there is a significant number of people actually contributing here who >> use it that would be all the better for some evidence. > Fair, and I shouldn't have leaned on an unquantified "growing." Let me > separate what I can back up from what I can't. > ... > What I can't do is hand you a survey. I don't have a count of contributors > who develop on Nix, and I'd rather admit that than dress up a guess. If the > bar for this is demonstrated contributor demand, that's a reasonable bar and > I'm happy to let the thread be the evidence, if it's just me and Tristan, so > be it; this can wait. I don't want to block this if there's actually a reasonable amount of demand. Let's wait a bit to see if other requestors show up. If we do go forward, I think the flake.nix file needs a header comment covering at least these points: 1. An explanation of what it is/does, aimed at people who never heard of Nix. Doesn't need to be long. (Some of our other root files could use some self-justification too :-() 2. A suggestion to add thus-and-such personal ~/.gitexclude patterns if you want to use Nix. regards, tom lane