From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: How to install GWL?
Date: Sat, 01 Feb 2020 12:49:32 +0100 [thread overview]
Message-ID: <87o8ui1q9f.fsf@gnu.org> (raw)
In-Reply-To: <87eevfubob.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 31 Jan 2020 12:07:16 +0100")
Hi there!
Ricardo Wurmus <rekado@elephly.net> skribis:
>> The difference between "as a package" --which implies inferiors-- or
>> "as a channel" is: embed vs extend.
>>
>> I was convinced that "as a package" was more convenient. Now I am not sure. :-)
>> Because we know what "embed" means. ;-)
>>
>> For example, Julien's home-manager [1] uses the "as a channel" approach.
>
> The home-manager *only* requires Guix. The GWL needs wisp,
> guile-commonmark, guile-gcrypt, guile-pfds (for sets),
> guile-syntax-highlight, graphviz (for visualizing workflows), etc. In
> the future it might also depend on the Guile AWS library, perhaps even
> some libraries that implement different schedulers, etc. I’ve also been
> thinking about adding a web interface to visualize the current state of
> processes spawned by the workflow, which should make debugging workflows
> much easier.
Oh, channels in their current form wouldn’t be a good fit because they
don’t allow you to ask for additional dependencies. Perhaps a problem
to solve, dunno.
> 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.
Yeah.
> 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.
Indeed, that makes sense to me.
Simon and I were discussing and I was saying that this inferior
vs. channel discussion reminds me of extend vs. embed in the context of
programming languages like Guile (where inferiors are a bit like
“embedding”).
But yeah, I didn’t have a good understanding of the constraints here, so
thanks for clarifying!
Ludo’.
next prev parent reply other threads:[~2020-02-01 11:50 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 [this message]
2020-02-05 13:50 ` zimoun
2020-02-05 13:46 ` 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=87o8ui1q9f.fsf@gnu.org \
--to=ludo@gnu.org \
--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).