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.94.2) (envelope-from ) id 1s1ARh-009w2k-Ee for pgsql-hackers@arkaria.postgresql.org; Sun, 28 Apr 2024 19:44:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s1ARe-00Dz94-LW for pgsql-hackers@arkaria.postgresql.org; Sun, 28 Apr 2024 19:44:19 +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.94.2) (envelope-from ) id 1s1ARe-00Dz8v-C7 for pgsql-hackers@lists.postgresql.org; Sun, 28 Apr 2024 19:44:19 +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.94.2) (envelope-from ) id 1s1ARc-000YBC-Py for pgsql-hackers@lists.postgresql.org; Sun, 28 Apr 2024 19:44:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 43SJiAbb790493; Sun, 28 Apr 2024 15:44:10 -0400 From: Tom Lane To: Alvaro Herrera cc: Peter Eisentraut , Greg Sabino Mullane , pgsql-hackers@lists.postgresql.org, Magnus Hagander Subject: Re: Tarball builds in the new world order In-reply-to: <202404281916.cpngjkjnosj2@alvherre.pgsql> References: <202404281916.cpngjkjnosj2@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Sun, 28 Apr 2024 21:16:48 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <790491.1714333450.1@sss.pgh.pa.us> Date: Sun, 28 Apr 2024 15:44:10 -0400 Message-ID: <790492.1714333450@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alvaro Herrera writes: > Why is it that the .gitrevision file is only created here, instead of > being added to the tarball that "git archive" produces? Adding an > argument like > --add-virtual-file $(distdir)/.gitrevision:$(GIT_REFSPEC) > to the git archive call should suffice. I think we don't want to do that. In the first place, it's redundant because "git archive" includes the commit hash in the tar header, and in the second place it gets away from the concept that the tarball contains exactly what is in our git tree. Now admittedly, if anyone's built tooling that relies on the presence of the .gitrevision file, they might prefer that we keep on including it. But I'm not sure anyone has, and in any case I think switching to the git-approved way of incorporating the hash is the best thing in the long run. What I'm thinking of doing, as soon as we've sorted the tarball creation process, is to make a test tarball available to the packagers group so that anyone interested can start working on updating their packaging process for the new approach. Hopefully, if anyone's especially unhappy about omitting .gitrevision, they'll speak up. regards, tom lane