all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Roel Janssen <roel@gnu.org>
Cc: gwl-devel@gnu.org
Subject: Re: How to install GWL?
Date: Thu, 23 Jan 2020 12:24:55 +0100	[thread overview]
Message-ID: <CAJ3okZ1mCMq2v0aQGu5pNgzWVRUCm1MAsh-4tatVRU0S+qXhPw@mail.gmail.com> (raw)
In-Reply-To: <d46ab068db3a77e5675cd8e80abfc82a1af05fa3.camel@gnu.org>

Hi Roel,

On Thu, 23 Jan 2020 at 12:16, Roel Janssen <roel@gnu.org> wrote:

> 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

I agree that with the current situation, it is confusing and hard to
know which "guix --version" is used when running "guix workflow".
It is what I tried to describe in my other email to this thread.


> What's the reason for not wanting GWL directly in Guix?

Maybe because it is proof-of-concept of "Guix is a Scheme library". :-)


All the best,
simon

  reply	other threads:[~2020-01-23 11:25 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ3okZ1mCMq2v0aQGu5pNgzWVRUCm1MAsh-4tatVRU0S+qXhPw@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gwl-devel@gnu.org \
    --cc=roel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.