From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: `--run=simple` error ?
Date: Fri, 22 Feb 2019 17:55:00 +0100 [thread overview]
Message-ID: <CAJ3okZ1i=rtonGGkye98w9ne-RVCfOPFCxOKUARBf=jNxi+zSg@mail.gmail.com> (raw)
In-Reply-To: <87y3673hoi.fsf@elephly.net>
Hi Ricardo,
On Fri, 22 Feb 2019 at 17:35, Ricardo Wurmus <rekado@elephly.net> wrote:
> No, the version of Guile is not at fault here. It’s about the version
> of Guix.
>
> (The GWL builds with Guix as an input.)
Ok.
> I’m not sure what’s the best way to install the GWL, to be honest.
From my opinion, it is similar than emacs-guix, isn't it?
> Should it be a mere channel that extends the *current* Guix? If it is
> built with Guix then it refers to an older version of Guix (namely the
> older version that is available through Guix itself), so that’s not
> actually desirable.
I agree.
> I think it should work with “guix pull” to stay current and ensure that
> it has access to the same packages that a user would see on the command
> line. Currently, this only works through a channel. I don’t really
> like that, though.
You have proposed something like: “~/.config/guix/current/bin/guix repl”
Why do you not like the channel and kind of inferior solution?
All the best,
simon
next prev parent reply other threads:[~2019-02-22 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 15:22 `--run=simple` error ? zimoun
2019-02-21 15:40 ` Ricardo Wurmus
2019-02-22 16:22 ` zimoun
2019-02-22 16:33 ` Pjotr Prins
2019-02-22 16:48 ` zimoun
2019-02-22 16:57 ` Pjotr Prins
2019-02-22 21:05 ` zimoun
2019-02-22 21:18 ` Pjotr Prins
2019-02-24 11:40 ` zimoun
2019-02-24 12:02 ` Pjotr Prins
2019-02-22 16:35 ` Ricardo Wurmus
2019-02-22 16:55 ` zimoun [this message]
2019-02-22 17:04 ` Ricardo Wurmus
2019-02-22 21:10 ` zimoun
2019-02-22 22:54 ` Ricardo Wurmus
2019-02-24 11:56 ` zimoun
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ1i=rtonGGkye98w9ne-RVCfOPFCxOKUARBf=jNxi+zSg@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
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).