From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roel Janssen Subject: Re: [PATCH] gnu: Add r-edger. Date: Tue, 24 May 2016 23:45:55 +0200 Message-ID: <87vb236sfg.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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36977) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b5K9R-0004iT-W2 for guix-devel@gnu.org; Tue, 24 May 2016 17:46:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b5K9P-0004w0-Pn for guix-devel@gnu.org; Tue, 24 May 2016 17:46:08 -0400 In-reply-to: <8737p7bxg6.fsf@gnu.org> 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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel Ludovic Courtès writes: > Roel Janssen skribis: > > [...] > >>>> This can be completely automated, so I don't think it has to be a lot of >>>> work: >>>> 1. guix package --export-source-tarballs=/var/www/public_html/ >>> >>> We could do this, but I figured we might as well let others do it. :-) >>> Currently we have tarballs.nixos.org, and I think there’ll be another >>> one pretty soon. Hopefully that’ll cover our needs. >>> >>> Thoughts? >> >> 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’s 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. >> 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’t be able to generate the cache on the fly like > ‘guix publish’ does because the daemon does not store raw 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. > FWIW I don’t have plans to work on it in the near future, so > contributions are welcome! ;-) It seems like a task I can work on. However, I am working on some other things that I would like to finish first. So if anyone else is interested in this.. :-) Kind regards, Roel Janssen