unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Jookia <166291@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: The tricky case of "--localstatedir=/var"
Date: Wed, 17 Feb 2016 00:06:25 -0800	[thread overview]
Message-ID: <874md7yd4u.fsf@gmail.com> (raw)
In-Reply-To: <20160216135729.GB13560@novena-choice-citizen.lan> (Jookia's message of "Wed, 17 Feb 2016 00:57:29 +1100")

Jookia <166291@gmail.com> writes:

> Over the past month a few people (myself included) have been hit by the 'gotcha'
> of not running ./configure with "--localstatedir=/var". It doesn't say this in
> the documentation but I question whether not having it as /var is a sane
> default. I'm sure this is somehow tied to the conventions of /usr/local.

I'm not sure there is a single default that will work for everybody. In
general, a value that is appropriate for one use case will not be
appropriate for a different use case.

For example, the README file in the root directory of Guix's git
repository [1] explains that if you want to re-build and re-install Guix
using a system that already runs Guix, it's important to explicitly set
the localstatedir variable to an appropriate value so that the new Guix
sees the existing items in the store. On GuixSD, I believe the
appropriate value would be "/var". Similarly, the Guix manual also
explains [2] that if you wish to have Guix and Nix share the same store,
you must explicitly set the localstatedir variable to an appropriate
value. According to the manual, if you're using Nix's defaults, then
that's "/nix/var". No single default value will satisfy both of those
use cases; somebody will always have to explicitly specify the
localstatedir.

Therefore, instead of worrying about what the "right" default should be,
perhaps it makes more sense to focus on how the documentation can be
improved. If setting the localstatedir is important, the manual should
explain that. The manual already mentions localstatedir, as shown above,
but perhaps the manual is not clear enough. People do seem to be
tripping over it.

With the aim of improving the documentation, then, I'll ask: what was
your use case? Why did you need to set the localstatedir explicitly? Is
there a place in the manual where, if information about the
localstatedir had been present, you would have realized from the start
that you needed to set it, and you would have understood what the
appropriate value to use was?

Best regards,
Chris

[1] README file: http://git.savannah.gnu.org/cgit/guix.git/tree/README
[2] Info node "(guix) Requirements": https://www.gnu.org/software/guix/manual/html_node/Requirements.html

  parent reply	other threads:[~2016-02-17  8:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 13:57 The tricky case of "--localstatedir=/var" Jookia
2016-02-16 14:29 ` Ricardo Wurmus
2016-02-16 14:52   ` Jookia
2016-02-16 16:41   ` Andreas Enge
2016-02-16 17:12     ` Jookia
2016-02-16 17:16       ` Andreas Enge
2016-02-16 16:04 ` Tobias Geerinckx-Rice
2016-02-16 16:08   ` Tobias Geerinckx-Rice
2016-02-16 19:11 ` Christopher Allan Webber
2016-02-16 19:59 ` Danny Milosavljevic
2016-02-16 22:42   ` Mark H Weaver
2016-02-17  9:29     ` Ricardo Wurmus
2016-02-17  8:06 ` Chris Marusich [this message]
2016-02-17  8:38   ` Jookia
2016-02-17  9:15     ` Chris Marusich
2016-02-17 10:08       ` Jookia
2016-02-17 17:50         ` Chris Marusich
2016-02-17 18:00           ` Jookia
2016-02-17 18:23           ` Andreas Enge
2016-03-17 22:11 ` Ludovic Courtès
2016-03-17 22:19   ` Mathieu Lirzin
2016-03-18  1:12   ` Jookia
2016-03-18 18:45     ` Ludovic Courtès
2016-03-19  3:27       ` Jookia
2016-03-19 14:11   ` 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=874md7yd4u.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=166291@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).