unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: gwl-devel@gnu.org
Subject: Re: How to install GWL?
Date: Thu, 23 Jan 2020 11:06:32 +0100	[thread overview]
Message-ID: <87y2tyv653.fsf@elephly.net> (raw)
In-Reply-To: <8736c755xf.fsf@kyleam.com>


Kyle Meyer <kyle@kyleam.com> writes:

> Hi Ricardo,
>
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> 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”.
>>
>> If we stick with installing the workflow language as a package, how
>> should package installation be handled?  Should all workflows require a
>> channels definition for reproducibility, so that we could instantiate an
>> inferior Guix using the exact specified version?  If none is provided we
>> could fall back to the latest version of Guix.
>>
>> How does that sound?
>
> The last combination sounds good to me: support/encourage specifying the
> channel definition in the workflow, and fall back to the latest version
> of Guix.  Though perhaps it'd be better to fall back to the user's
> current version instead?  My thinking is that the user's version would
> be a less frequently moving target, be more likely to have higher
> substitute availability, and would more closely match any debugging and
> testing the user is doing with, say, `guix environment'.

Yes, I agree.  I suppose we could achieve this by simply spawning “guix
repl” and rely on the environment to give us the user’s current version
of Guix.  Then we connect to the spawned REPL.

-- 
Ricardo

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

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=87y2tyv653.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=gwl-devel@gnu.org \
    --cc=kyle@kyleam.com \
    /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).