unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kyle <kyle@posteo.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Help adding a graph backend
Date: Fri, 10 Feb 2023 19:03:01 +0000	[thread overview]
Message-ID: <87DCA146-6CBE-4C3A-8415-2DE92951361A@posteo.net> (raw)
In-Reply-To: <Y+YOyQ4BFt0xJJJa@jurong>

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

Thanks, Andreas! 

For my own education I just tried running ./configure with no arguments on Ubuntu and it ran without error. I wasnt actually able to run pre-inst-env afterwards though since I am not an administrator on that system. That behavior, though, seems consistent with what I think you are saying: setting up pre-inst-env is currently easier by default for foreign distro users than for guixsd users. I can see how that made perfect sense when Guix was only used with a foreign distro. I don't know much about what is actually happening in ./configure, but it also makes sense to me that the default now should depend on what the host system actually is. Then the manual could include those standard lines in a source block explicitly and it will all seem routine and not at all scary to people like me. It already seems smart enough to do that given it could make the right suggestion in my case.

On February 10, 2023 4:30:49 AM EST, Andreas Enge <andreas@enge.fr> wrote:
>Hello Kyle,
>
>Am Fri, Feb 10, 2023 at 03:10:02AM +0000 schrieb Kyle Andrews:
>> configure: error: chosen localstatedir '/usr/local/var' does not match that of the existing installation '/var'
>
>you should do exactly as suggested: Before running "make", configure the
>Guix source code not by "./configure", but
>   ./configure --localstatedir=/var
>
>Personally I think this is a bug in Guix: It was chosen to follow the
>standard configure behaviour (installation directories under /usr/local).
>But it would probably be better to let the Guix behaviour be the one
>that everybody wants (especially newcomers), and to leave options like
>--localstatedir to people needing to do something unusual.
>
>Andreas
>

[-- Attachment #2: Type: text/html, Size: 2130 bytes --]

      reply	other threads:[~2023-02-10 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  3:10 Help adding a graph backend Kyle Andrews
2023-02-10  7:11 ` Julien Lepiller
2023-02-10  9:25 ` Attila Lendvai
2023-02-10  9:30 ` Andreas Enge
2023-02-10 19:03   ` Kyle [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

  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=87DCA146-6CBE-4C3A-8415-2DE92951361A@posteo.net \
    --to=kyle@posteo.net \
    --cc=andreas@enge.fr \
    --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).