From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Vollmert Subject: Re: git-fetch origin output is read-only - and reproducibility Date: Mon, 29 Jul 2019 17:58:02 +0200 Message-ID: References: <20190729165743.04e6a516@scratchpost.org> <87k1c07sdf.fsf@elephly.net> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:53404) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hs82T-0008KN-U4 for guix-devel@gnu.org; Mon, 29 Jul 2019 11:58:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hs82S-0001PS-Tj for guix-devel@gnu.org; Mon, 29 Jul 2019 11:58:17 -0400 Received: from mx2.mailbox.org ([80.241.60.215]:9744) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hs82S-0001O0-MU for guix-devel@gnu.org; Mon, 29 Jul 2019 11:58:16 -0400 In-Reply-To: <87k1c07sdf.fsf@elephly.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel@gnu.org > On 29. Jul 2019, at 17:49, Ricardo Wurmus wrote: >> currently, when using the git-fetch origin, the resulting source will = have >> all files read-only. Further phases trying to do reproducibility = patches have >> to manually chmod in order to be able to patch. >>=20 >> Can we change that? For example change what this origin does or = change what >> the build systems do by default? >=20 > I think this would be good. It=E2=80=99s a little annoying when = switching from > a tarball to git-fetch because you=E2=80=99ll have to add a phase that = makes all > files writable. >=20 > This would probably have to be changed in the unpack phase of the > gnu-build-system, which copies files recursively when the sources are = a > directory (instead of a tarball). At the risk of getting slightly off-topic, I was very surprised when I = figured out that such things were left to the build system. Couldn=E2=80=99t the = source/origin abstraction consistently refer a directory tree *or* a tarball? Cheers Robert