unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: what colour should the bikeshed have?
Date: Mon, 24 Jun 2019 15:33:46 +0200	[thread overview]
Message-ID: <875zovt8ed.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ2MnM76cean6KXMYGcOSGGnpOOTmpQjQ67vD7u0zePRnA@mail.gmail.com>


zimoun <zimon.toutoune@gmail.com> writes:

> However, I am a bit lost. Does this process still work?
>
> process: sleep
>   packages "coreutils"
>   run '(begin (display "Sleeping...\n")
>                     (system* "sleep" "10"))

Yes.  The “procedure” field takes a plain S-expression, a G-expression,
or a code-snippet (which is what the “# ”-syntax produces).

> For consistency, why not?
>   run # guile {
>     blah
>   }

Because it’s unnecessary.  You can do this if you want a particular
variant of Guile, of course.

> And, is it better to declare explicitly "coreutils" as package input
> when using bash?
> Or implicitly? For example, if `run # python {}` is used then the
> package input is implicitly python.
> What do you think?

I want this to be implicit, but currently this is not yet possible.
Guix has no mechanism to collect inputs from G-expressions, so we can’t
automatically add the required inputs to the execution environment.
Ludo has a patch for remote evaluation, though, which adds features that
we can use for this purpose.

--
Ricardo

  reply	other threads:[~2019-06-24 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 13:14 what colour should the bikeshed have? Ricardo Wurmus
2019-06-24 10:23 ` zimoun
2019-06-24 13:33   ` Ricardo Wurmus [this message]
2019-06-25 15:32   ` Ricardo Wurmus
2019-06-24 22:24 ` Ricardo Wurmus

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=875zovt8ed.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=gwl-devel@gnu.org \
    --cc=zimon.toutoune@gmail.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).