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: Tue, 25 Jun 2019 17:32:44 +0200	[thread overview]
Message-ID: <87mui5smsv.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"))

I should note that this will *not* work in a container because “sleep”
would not be found in the container environment.

> And, is it better to declare explicitly "coreutils" as package input
> when using bash?

“coreutils” only needs to be specified when they are used.  We need it
in the example because “sleep” is provided by “coreutils”.  That’s
unrelated to the use of Bash.

> Or implicitly? For example, if `run # python {}` is used then the
> package input is implicitly python.
> What do you think?

This is still on my list for when G-expressions are used (and it depends
on features that are waiting to arrive in Guix), but I just added
another convenience in commit 82ba9bad073d717c9e6fd9cf243cd6d94f674283.

If you don’t really care for bash and just want to use a shell you can
leave off the interpreter and default to /bin/sh.  This works now:

  process: greet
    packages "hello"
    # { hello }

--
Ricardo

  parent reply	other threads:[~2019-06-25 15:32 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
2019-06-25 15:32   ` Ricardo Wurmus [this message]
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=87mui5smsv.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).