all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: Removing the need for ./configure --localstatedir=/var ?
Date: Thu, 7 Sep 2017 22:14:38 +0300	[thread overview]
Message-ID: <20170907191438.GI2239@macbook42.flashner.co.il> (raw)
In-Reply-To: <87bmmm30iq.fsf@dustycloud.org>

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

On Thu, Sep 07, 2017 at 12:02:43PM -0500, Christopher Allan Webber wrote:
> Every now and then I rebuild Guix and hit the problem where I run
> ./configure and then I am reminded that I need to instead do:
> 
>   ./configure --localstatedir=/var
> 
> IIRC this is because of GNU standards about default paths and pretty
> much no other reason that we don't default to /var.  But I think Guix is
> a special case.
> 
> Should we ask maybe for an exception?  There's no reason for users to
> bump into this.  It's annoying even for me, and at least I know (or
> think I do) why.
> 
>  - Chris
> 

I've made sure to also pass --sysconfdir=/etc so that /etc/guix/acl
doesn't end up in /usr/local/etc/guix/acl, leading to a split between
`guix foo' and './pre-inst-env guix foo'.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-09-07 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 17:02 Removing the need for ./configure --localstatedir=/var ? Christopher Allan Webber
2017-09-07 19:14 ` Efraim Flashner [this message]
2017-09-10 21:10 ` Ludovic Courtès
2017-09-12  1:18   ` Christopher Allan Webber

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=20170907191438.GI2239@macbook42.flashner.co.il \
    --to=efraim@flashner.co.il \
    --cc=cwebber@dustycloud.org \
    --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.