all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: Removing the need for ./configure --localstatedir=/var ?
Date: Sun, 10 Sep 2017 23:10:08 +0200	[thread overview]
Message-ID: <87d16y45vz.fsf@gnu.org> (raw)
In-Reply-To: <87bmmm30iq.fsf@dustycloud.org> (Christopher Allan Webber's message of "Thu, 07 Sep 2017 12:02:43 -0500")

Christopher Allan Webber <cwebber@dustycloud.org> skribis:

> 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?

No need to ask.  :-)

> 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.

I think it would be surprising to users who install from source if
localstatedir is not under $prefix by default (someone who wants to
install to /opt/foo would be surprised to find out that some files go to
/var instead of /opt/foo/var.)

There’s also the question of “make dist”, which should still DTRT.

We could have $prefix default to /… but that’s not quite what one might
expect either.

I think the current situation is a good middle ground, even though I can
also sympathize with your frustration.

Thoughts?

It’s weird how a simple question like this can be seemingly this complex
to address.  :-)

Ludo’.

  parent reply	other threads:[~2017-09-10 21:10 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
2017-09-10 21:10 ` Ludovic Courtès [this message]
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=87d16y45vz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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.