unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Brian Woodcox <bw@inskydata.com>
To: help-guix@gnu.org, ison@airmail.cc
Subject: Re: Having a problem invoking curl only when using guix pull
Date: Thu, 16 May 2019 16:53:35 -0600	[thread overview]
Message-ID: <98FF32C2-9951-45EE-A08D-DBED578C004A@inskydata.com> (raw)

> Perhaps all you need is to include the curl package in your package's
> native-inputs field.
> 
> Also as a side note, I'm not entirely sure if using open-input-pipe would be
> considered good practice for packages as far as reproducibility is concerned.
> Perhaps someone else can comment on that.
> But another option you might want to consider is using the built in web modules.
> For example:
> 
>   #:use-module (web client)
>   #:use-module (web uri)
>   ...
>     (let* ((out (call-with-values (lambda () (http-get (string->uri %api-url)))
>                   (lambda (response body) body)))
>            ...
> 
> I'm not sure if that's the most elegant way to do it, but it seems to work.
> There's also a curl module for guile, although I'm not sure if guix will let you
> import it or not.

Hi ison,

Unfortunately that doesn’t work, due to tls not being available.

See the bug I reported here —> https://lists.gnu.org/archive/html/bug-guile/2019-04/msg00008.html <https://lists.gnu.org/archive/html/bug-guile/2019-04/msg00008.html>

Thanks for the effort though.

Brian.

             reply	other threads:[~2019-05-16 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 22:53 Brian Woodcox [this message]
2019-05-17  0:21 ` Having a problem invoking curl only when using guix pull John Soo
2019-05-17  0:31   ` Brian Woodcox
2019-05-17  1:04   ` Tobias Geerinckx-Rice
  -- strict thread matches above, loose matches on Subject: below --
2019-05-14 22:23 Brian Woodcox
2019-05-16  3:13 ` ison
2019-05-16 21:49 ` Brian Woodcox

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=98FF32C2-9951-45EE-A08D-DBED578C004A@inskydata.com \
    --to=bw@inskydata.com \
    --cc=help-guix@gnu.org \
    --cc=ison@airmail.cc \
    /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).