unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: You say nix, I say guix: Nix 2.0 and Guix
Date: Sun, 29 Apr 2018 19:34:09 +0200	[thread overview]
Message-ID: <87k1sp3oj2.fsf@gnu.org> (raw)
In-Reply-To: <87d0yjkrv2.fsf@gmail.com> (Chris Marusich's message of "Sat, 28 Apr 2018 13:17:53 -0700")

Hello!

Chris Marusich <cmmarusich@gmail.com> 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 2.0 does that.  That’s something we could borrow.

> Is compatibility with the nix-daemon a goal of the Guix project?

I’ve come to the conclusion that it’s not a worthy goal, as in, it would
cost more than it’s worth.  guix-daemon is already incompatible with
nix-daemon on a few things, such as the “builtin:download” derivation
builder.

> Can we take inspiration from any of the non-daemon features and use
> them in Guix?

Definitely.

> 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.

I’m also hopeful that we can move to a Guile-based daemon in the future.

Overall, I think Nix and Guix still have a lot to share, probably not in
terms of code, but at least in terms of design, features, and ideas.
The discussions with Eelco at the Guix Workshop demonstrated that!

Ludo’.

  reply	other threads:[~2018-04-29 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28 20:17 You say nix, I say guix: Nix 2.0 and Guix Chris Marusich
2018-04-29 17:34 ` Ludovic Courtès [this message]
2018-04-29 17:54   ` Mark H Weaver
2018-04-29 17:44 ` Nils Gillmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1sp3oj2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).