From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: You say nix, I say guix: Nix 2.0 and Guix Date: Sun, 29 Apr 2018 13:54:48 -0400 Message-ID: <876049yk2f.fsf@netris.org> References: <87d0yjkrv2.fsf@gmail.com> <87k1sp3oj2.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]:50830) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fCqY9-0000oS-6V for guix-devel@gnu.org; Sun, 29 Apr 2018 13:55:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fCqY6-00077s-4G for guix-devel@gnu.org; Sun, 29 Apr 2018 13:55:49 -0400 In-Reply-To: <87k1sp3oj2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 29 Apr 2018 19:34:09 +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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Chris Marusich skribis: > >> On February 22nd, Nix 2.0 was released: >> >> https://nixos.org/nix/manual/#ssec-relnotes-2.0 > > Very nice work. It looks like the CLI is closer to that of Guix now. :-) > >> It contains a lot of interesting new features. Are there any plans to >> merge some of the nix-daemon changes into our guix-daemon? > > Why not? What did you have in mind? One thing we discussed long ago > was the idea of keeping signatures in the store database, and I think > Nix=C2=A02.0 does that. That=E2=80=99s something we could borrow. [...] >> Conversely, is there anything we can upstream to Nix that they might >> find useful? > > Changes in the daemon are pretty much the only thing we could upstream, > and I used to do exactly that. At some point I decided to stop > following closely upstream and allow ourselves to change the daemon as > we see fit. As a result, you may find that not every change that we > make to our nix/ directory is directly applicable to current Nix. One possible complication with exchanging code with nix-daemon is that a few years ago, nix-daemon apparently switched to a multithreaded model, whereas guix-daemon deliberately avoids threads in the daemon. See: https://lists.gnu.org/archive/html/guix-devel/2014-12/msg00363.html That said, I haven't followed Nix development, so I don't know what has happened with nix-daemon since then, nor how much this would affect code sharing in practice. Mark