all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Buttery Pancake <butterypancake@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix Paths
Date: Mon, 21 Sep 2020 11:13:29 +0200	[thread overview]
Message-ID: <87wo0nsdae.fsf@elephly.net> (raw)
In-Reply-To: <zEzQsaVuLsL3sFv9Qe3zyU_6AJVhOBpxXYmj66jn_ZudGq5BqGuO-nmCkdcCdevp3Jel7r5wHyud3KgtyHfaqLsL_xbvmOCj36hsWJ328kU=@protonmail.com>


> I am wondering why Guix chose `/var/guix` path instead of
> `/gnu/var/guix` or `/guix/var/guix`, as Nix uses `/nix/var/nix`?

I think there’s no better reason than to say that /var is the
conventional local state directory on GNU systems.

It’s possible to use /gnu/var/guix, of course; on the HPC cluster at the
MDC we use /gnu/var as the localstatedir, but it’s not as convenient as
it may seem, because that directory contains the profile directories,
which need to be user-writable, whereas the rest of /gnu only need to be
writable by the daemon.  This means that we end up mounting the same
directories more than once with different permissions.

Users can pick anything for the localstatedir during the configure step
and “guix pull” should respect that choice in the long term.

-- 
Ricardo


  parent reply	other threads:[~2020-09-21  9:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  1:32 Guix Paths Buttery Pancake
2020-09-21  8:33 ` Andreas Enge
2020-09-21  9:06 ` Tobias Geerinckx-Rice
2020-09-21  9:13 ` Ricardo Wurmus [this message]
2020-09-21 14:45   ` Buttery Pancake
2020-09-21 15:06     ` Tobias Geerinckx-Rice

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

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

  git send-email \
    --in-reply-to=87wo0nsdae.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=butterypancake@protonmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.