From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, gwl-devel@gnu.org
Subject: Re: How to install GWL?
Date: Wed, 5 Feb 2020 14:46:32 +0100 [thread overview]
Message-ID: <CAJ3okZ0ZLAsS+bbRJkPUW1jEVK2UDKJ9Vi8JtU8FCaS-w82JGw@mail.gmail.com> (raw)
In-Reply-To: <87eevfubob.fsf@elephly.net>
Hi Ricardo,
On Fri, 31 Jan 2020 at 12:07, Ricardo Wurmus <rekado@elephly.net> wrote:
> Channels don’t allow for any fancy installation or setup. The Guile
> modules provided by a channel are compiled just in time when running
> “guix pull”. It doesn’t seem like a good idea for the GWL to hook into
> the channels mechanism when it doesn’t provide what channels were
> designed to help implement: extensions to the package graph.
I got it. :-)
> I think inferiors also give GWL users a feature that would otherwise be
> missing: to run arbitrary workflows with arbitrary channel definitions
> via inferiors without having to first manually execute “guix pull” to
> switch to the particular channels that a workflow requires. Using
> inferiors gives a superior user experience, in my opinion.
I understand.
Thank you for explaining. Now, it is all clear to me.
Cheers,
simon
prev parent reply other threads:[~2020-02-05 13:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 21:55 How to install GWL? Ricardo Wurmus
2020-01-23 1:15 ` Kyle Meyer
2020-01-23 10:06 ` Ricardo Wurmus
2020-02-01 9:26 ` Ricardo Wurmus
2020-02-05 14:34 ` zimoun
2020-02-05 19:36 ` Ricardo Wurmus
2020-02-10 0:22 ` zimoun
2020-01-23 1:17 ` zimoun
2020-01-23 11:14 ` Roel Janssen
2020-01-23 11:24 ` zimoun
2020-01-23 13:02 ` Ricardo Wurmus
2020-01-23 14:18 ` zimoun
2020-01-23 13:12 ` Ricardo Wurmus
2020-01-31 9:16 ` zimoun
2020-01-31 11:07 ` Ricardo Wurmus
2020-02-01 11:49 ` Ludovic Courtès
2020-02-05 13:50 ` zimoun
2020-02-05 13:46 ` zimoun [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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ0ZLAsS+bbRJkPUW1jEVK2UDKJ9Vi8JtU8FCaS-w82JGw@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=ludo@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).