unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: statedir locations
Date: Tue, 28 Jan 2014 00:05:04 -0500	[thread overview]
Message-ID: <874n4ohf27.fsf@netris.org> (raw)
In-Reply-To: <874n4piish.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 27 Jan 2014 15:46:54 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Mark H Weaver <mhw@netris.org> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> John Darrington <john@darrington.wattle.id.au> skribis:
>>>
>>>> It has come to my attention that guix packages (at least those with gnu build system)
>>>> default their statedirs to directories under /nix/store/.  Recall that the statedirs (ie: 
>>>> sharedstatedir localstatedir and runstatedir) are for installing data files *which the programs
>>>> modify while they run* [1].   Obviously a program cannot modify anything under /nix/store
>>>> I think we need to update the default configure flags.
>>>
>>> Yes.  We actually have a number of local modifications:
>>>
>>>   $ grep -e --localstatedir gnu/packages/*.scm | wc -l
>>>   5
>>>
>>> I think we should change gnu-build-system.scm to pass
>>> --localstatedir=/var, unless ‘configure-flags’ specify another setting.
>>>
>>> I’ll do that in ‘core-updates’.
>>
>> What about 'sharestatedir' and 'runstatedir'?
>
> ‘runstatedir’ is in the not-yet-released Autoconf, but otherwise, yeah,
> they all deserve the same treatment.

So there's a problem.  Lots of builds are now failing, because "make
install" often tries to create /var or /com and does not have sufficient
permissions to do so.

I'm not sure what to do about this.

      Mark

  reply	other threads:[~2014-01-28  5:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 11:50 statedir locations John Darrington
2014-01-27 12:57 ` Ludovic Courtès
2014-01-27 13:44   ` Mark H Weaver
2014-01-27 14:46     ` Ludovic Courtès
2014-01-28  5:05       ` Mark H Weaver [this message]
2014-01-28  9:49         ` Ludovic Courtès
2014-01-27 22:48   ` Ludovic Courtès
2014-01-28  9:23     ` Ludovic Courtès
2014-01-28 17:53       ` John Darrington
2014-01-28 22: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=874n4ohf27.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).