From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: statedir locations
Date: Tue, 28 Jan 2014 23:11:21 +0100 [thread overview]
Message-ID: <87iot3daeu.fsf@gnu.org> (raw)
In-Reply-To: <20140128175358.GA29551@jocasta.intra> (John Darrington's message of "Tue, 28 Jan 2014 18:53:58 +0100")
John Darrington <john@darrington.wattle.id.au> skribis:
> On Tue, Jan 28, 2014 at 10:23:16AM +0100, Ludovic Court??s wrote:
>
> I was overconfident: the patch broke everything, because
> Automake-generated makefiles typically try to mkdir $localstatedir:
>
> http://hydra.gnu.org/eval/45514
>
> So I just reverted it, and I think we???re stuck with the status quo until
> someone has a better idea.
>
> So the status quo is, that these packages mkdir /nix/store.../var/com .
> Presumably they do that for a reason, viz the program needs to write
> to these directories.
Right. Apparently Automake doesn’t emit anything for packages that do
not use the ‘localstate’ prefix.
> But they will not be able to do that because /nix/store is immutable.
> These programs will then break. :(
Well, yes.
> For the longer term, we could submit an Automake patch such that it
> doesn???t insist on creating $localstatedir et al.
>
> That sounds like a good idea. In the meantime, couldn't we patch the generated Makefile.in so that it will not die if the mkdir fails?
Yes, as done for DBus for instance. Unfortunately, I don’t see any
obvious way to do that patching automatically.
Thanks,
Ludo’.
prev parent reply other threads:[~2014-01-28 22:16 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
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 [this message]
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=87iot3daeu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.