unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Schäfer" <git@danielschaefer.me>
To: guix-devel@gnu.org
Subject: Compatibility between Nix and Guix
Date: Thu, 26 Sep 2019 04:13:05 +0200	[thread overview]
Message-ID: <b873e745-c514-671d-b2ad-be8fb5bce7ee@danielschaefer.me> (raw)

[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]

Hi all,

I've been using NixOS for a few years and now I want to try out Guix.
The goal is to see whether there is a benefit to using both and what we can learn from each other.

Last year Ludo wrote:
> > 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.

But the Guix manual at 2.2 [1] says:
> When a working installation of the Nix package manager is available, you can
> instead configure Guix with --disable-daemon. In that case, Nix replaces the
> three dependencies above.
> 
> Guix is compatible with Nix, so it is possible to share the same store between
> both. To do so, you must pass configure not only the same --with-store-dir
> value, but also the same --localstatedir value. The latter is essential because
> it specifies where the database that stores metadata about the store is
> located, among other things. The default values for Nix are
> --with-store-dir=/nix/store and --localstatedir=/nix/var. Note that
> --disable-daemon is not required if your goal is to share the store with Nix. 

How much of that is still true? The daemon is not compatible anymore and
I don't think it is a good idea to have two different daemons share the same store.

Is there still the a possibility to use either Nix on GuixSD or Guix on NixOS
without duplicating the store or running two daemons?
Or e.g. use Nix with Guile?

Cheers,
Daniel

[1] https://guix.gnu.org/manual/en/guix.html#Requirements


[-- Attachment #2: Type: text/html, Size: 1954 bytes --]

             reply	other threads:[~2019-09-26  2:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26  2:13 Daniel Schäfer [this message]
2019-09-26 12:19 ` Compatibility between Nix and Guix Pjotr Prins
2019-09-27 13:25   ` Tobias Geerinckx-Rice via Development of GNU Guix and the GNU System distribution.
2019-09-27 20:00     ` Ricardo Wurmus
2019-09-28 15:38       ` Tobias Geerinckx-Rice
2019-09-28 21:15         ` Ludovic Courtès

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=b873e745-c514-671d-b2ad-be8fb5bce7ee@danielschaefer.me \
    --to=git@danielschaefer.me \
    --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).