From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: [PATCH] gnu: Add r-edger. Date: Thu, 26 May 2016 10:01:37 +0200 Message-ID: <87wpmhjli6.fsf@gnu.org> References: <87lh3r61ab.fsf@gnu.org> <20160523015421.GA22738@jasmine> <20160523080851.GA23593@debian-netbook> <87eg8tw2hl.fsf@gnu.org> <87d1ocl9zc.fsf@gnu.org> <8737p8wgmk.fsf@gnu.org> <8737p7bxg6.fsf@gnu.org> <87vb236sfg.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56458) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5qEl-0004GL-Ci for guix-devel@gnu.org; Thu, 26 May 2016 04:01:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b5qEh-0007eA-9S for guix-devel@gnu.org; Thu, 26 May 2016 04:01:46 -0400 In-Reply-To: <87vb236sfg.fsf@gnu.org> (Roel Janssen's message of "Tue, 24 May 2016 23:45:55 +0200") 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: Roel Janssen Cc: guix-devel Roel Janssen skribis: > Ludovic Court=C3=A8s writes: > >> Roel Janssen skribis: [...] >>> I'd say we should definitely do this. Making the Guix project >>> self-contained will make it look more solid to people outside of the >>> project. This is an issue we have solved half-way now.. We rely on >>> infrastructure we cannot easily create with Guix only. >> >> What part of the infrastructure do you have in mind? It=E2=80=99s true = that we >> fetch sources from a wide range of places now. > > In this case, just a "content-addressed mirror" (we don't have the ui to > create it). So, we have the code in place to fetch from other > content-addressed mirrors, but we don't have the code in place to create > one. OK. >>> I think it's important that we can show that with GNU Guix, we've got >>> everything covered, from source to binary, without relying on other >>> projects (even though Nix is a friendly project :-)) >>> >>> It doesn't matter if we actually create a content-addressed mirror any >>> time soon, what matters is that we provide the tools to do so easily. >> >> I agree. :-) A command to create a content-addressed cache along the >> lines of tarballs.nixos.org would be welcome, indeed, and rather easy to >> implement (we wouldn=E2=80=99t be able to generate the cache on the fly = like >> =E2=80=98guix publish=E2=80=99 does because the daemon does not store ra= w content >> hashes; instead, it stores the hash of the nar of the contents, but >> anyway a detail.) > > Could we create a mapping between the hash from the package recipe and > the hash of the nar of the contents? Then this wouldn't be a problem. This sounds like a description of how Guix works. ;-) Roughly, objects compile down to derivations, and there=E2=80=99s= a mapping from the derivation name (the .drv file) to its outputs. The same is true of origins, which (usually) compile to fixed-output derivations. Now, store items are not necessarily plain regular files, which is why the daemon stores the hash of their nar-serialization. Cheers, Ludo=E2=80=99.