From: Roel Janssen <roel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>, gwl-devel@gnu.org
Subject: Re: How to install GWL?
Date: Thu, 23 Jan 2020 12:14:47 +0100 [thread overview]
Message-ID: <d46ab068db3a77e5675cd8e80abfc82a1af05fa3.camel@gnu.org> (raw)
In-Reply-To: <875zh3w3yp.fsf@elephly.net>
Hi Ricardo,
On Wed, 2020-01-22 at 22:55 +0100, Ricardo Wurmus wrote:
> Hi,
>
> the GWL is intended to be an extension of Guix. It uses Guix in two
> ways:
>
> 1) it uses modules provided by Guix as one would use a
> library. These
> include (guix gexp), (guix derivations), (guix monads), (guix store),
> etc.
>
> 2) it uses Guix to install packages at runtime based on whatever
> workflow a user asks to be run.
>
> The “gwl” package has the “guix” package among its inputs due to 1).
> This version of Guix will always be somewhat old, and older than the
> version of Guix used to install the GWL. This is okay for using Guix
> modules, but it wouldn’t be okay for 2).
I initially wanted the GWL to be part of Guix, and I think that could
greatly simplify things. So by installing GWL, you get the "workflow"
and "process" subcommands that work with the version of Guix returned
by:
$ guix --version
This would require us to package GWL in such a way that it doesn't have
Guix as one of its inputs. Is that possible?
> How should the GWL be installed for maximum convenience and
> compatibility? Does it make sense to install it as a channel so that
> it
> is tied to the user’s current version of Guix? That would be pretty
> awkward and less convenient than just typing “guix install gwl”.
Or.. we merge the code from GWL into Guix, so it's automatically there;
no install needed.
I think the code is quite lightweight, and since it uses the Guix
modules, it is somewhat tied to a specific version of Guix.
What's the reason for not wanting GWL directly in Guix?
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2020-01-23 11:14 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 [this message]
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
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=d46ab068db3a77e5675cd8e80abfc82a1af05fa3.camel@gnu.org \
--to=roel@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).