From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>,
41458@debbugs.gnu.org
Subject: bug#41458: Misleading error message when call guix command using pre-inst-env script
Date: Mon, 25 May 2020 19:31:14 +0200 [thread overview]
Message-ID: <CAJ3okZ3FZiyroNePNP9ZnYRp=KupzEEkqhYye1ECH8WDwcd07g@mail.gmail.com> (raw)
In-Reply-To: <87367q64e9.fsf@gnu.org>
Hi,
On Sat, 23 May 2020 at 17:47, Ludovic Courtès <ludo@gnu.org> wrote:
> Jérémy Korwin-Zmijowski <jeremy@korwin-zmijowski.fr> skribis:
> > $ git clone https://git.savannah.gnu.org/git/guix.git
> > $ cd guix
> > $ guix environment --pure guix
> > [dev]$ ./bootstrap && ./configure --localstatedir=/var && make
Hum? instead of these:
> > exit
> > $ ./pre-inst-env guix build artanis
what you (Jérémy) would want seems:
--8<---------------cut here---------------start------------->8---
[dev]$ ./pre-inst-env guix pull --url=$PWD -p /path/to/your/custom
[dev]$ exit
$ /path/to/your/custom/bin/guix build artanis
--8<---------------cut here---------------end--------------->8---
> This is a development environment issue that cannot happen when using a
> ‘guix pull’-provided ‘guix’ command. I would close it as “wontfix”
> since, after all, it’s just one of the many ways one can end up with a
> non-functional development environment.
Even, I would close it as 'notabug'. ;-)
Cheers,
simon
next prev parent reply other threads:[~2020-05-25 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 14:59 bug#41458: Misleading error message when call guix command using pre-inst-env script Jérémy Korwin-Zmijowski
2020-05-23 15:46 ` Ludovic Courtès
2020-05-25 17:31 ` zimoun [this message]
2020-05-31 18:50 ` Jérémy Korwin-Zmijowski
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='CAJ3okZ3FZiyroNePNP9ZnYRp=KupzEEkqhYye1ECH8WDwcd07g@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=41458@debbugs.gnu.org \
--cc=jeremy@korwin-zmijowski.fr \
--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).