all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: extract tools from guix scripts
Date: Thu, 08 Mar 2018 21:15:39 +0100	[thread overview]
Message-ID: <87bmfyl3x0.fsf@elephly.net> (raw)
In-Reply-To: <CAE4v=pgt_dsr2Jz2iimyhX8WPOFX9-OpQ-UnaTq0K7ygPSaW7g@mail.gmail.com>


Gábor Boskovits <boskovits@gmail.com> writes:

> 2018-03-08 20:01 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:
>
>> Hi Guix,
>>
>> under “guix/scripts” there are a couple of tools that are really useful,
>> such as “guix challenge”.  While they are great for the command line,
>> I’d really like to use them from within Guile.
>>
>> Using “(guix-challenge)” directly is cumbersome, because I need to
>> provide an argument list “args”, which is then parsed internally.
>> Instead, I’d like to be able to say
>>
>>    (challenge #:urls (list "a" "b")
>>               #:packages (list foo bar baz))
>>
>> and have it produce some report values.  Then “guix-challenge” could be
>> implemented in terms of “challenge”.
>>
>> The same might be useful for “guix-build” or “guix-environment”.
>>
>>
> I agree. This would also enable more flexible cli possibilities, and
> would be really useful for scripting. Does this idea fit to the
> improve command line tools outreachy idea?

The outreachy project is about making the *output* of Guix prettier and
less cluttered, so this would not be part of that project.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2018-03-08 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 19:01 extract tools from guix scripts Ricardo Wurmus
2018-03-08 20:12 ` Gábor Boskovits
2018-03-08 20:15   ` Ricardo Wurmus [this message]
2018-03-08 20:26     ` Gábor Boskovits
2018-03-09 23:32 ` Ludovic Courtès

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=87bmfyl3x0.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@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.