From: "Thompson, David" <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: pypi->guix script
Date: Mon, 8 Sep 2014 13:19:11 -0400 [thread overview]
Message-ID: <CAJ=RwfY8Wz+ri_6+XA0EUgH4No-bYy8QW5EgeMtk3wJme-WMoQ@mail.gmail.com> (raw)
In-Reply-To: <87bnqqgomp.fsf@gnu.org>
On Mon, Sep 8, 2014 at 10:42 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> "Thompson, David" <dthompson2@worcester.edu> skribis:
>
>> On Mon, Sep 8, 2014 at 3:06 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>
> [...]
>
>>> It would indeed be nice to turn it into a ‘guix pipy’ command or
>>> something like that. If need be, I can help with the details of
>>> integrating it.
>>>
>>
>> Yes, that would be nice. What are your thoughts on this?
>
> The way forward would be to drop the file as guix/scripts/pipy.scm, and
> then adjust it to follow the calling convention that ‘run-guix-command’
> expects. Similarly, it should use (guix build download).
>
> Since it uses Guile-JSON, maybe ./configure would have to check for its
> availability and disable compilation/installation when Guile-JSON is not
> found (in a way similar to BUILD_DAEMON_OFFLOAD, in config-daemon.ac.)
>
> Then a test file and an entry in the manual would be perfect.
>
Thanks for the explanation. I will add this to my list of projects. :)
- Dave
next prev parent reply other threads:[~2014-09-08 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 20:10 pypi->guix script David Thompson
2014-09-06 20:36 ` Nikita Karetnikov
2014-09-08 7:06 ` Ludovic Courtès
2014-09-08 13:42 ` Thompson, David
2014-09-08 14:42 ` Ludovic Courtès
2014-09-08 17:19 ` Thompson, David [this message]
2014-09-09 7:39 ` Ludovic Courtès
2014-09-09 13:05 ` Thompson, David
2014-09-09 14:11 ` Ludovic Courtès
2014-09-10 22:40 ` Cyril Roelandt
2014-09-10 22:29 ` Cyril Roelandt
2014-09-11 7:59 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ=RwfY8Wz+ri_6+XA0EUgH4No-bYy8QW5EgeMtk3wJme-WMoQ@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).