unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Amirouche Boubekki <amirouche@hypermove.net>
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>,
	Help-Guix <help-guix-bounces+amirouche=hypermove.net@gnu.org>
Subject: Re: guix with guile-next
Date: Fri, 07 Oct 2016 18:47:33 +0200	[thread overview]
Message-ID: <4ba270f1bf4607aa364d964b42210322@hypermove.net> (raw)
In-Reply-To: <CAJ98PDxHBz-5DA4Nvbh4gFG6U=Nxrr8MUvUHXA4usEYZO8t8cQ@mail.gmail.com>

On 2016-10-07 18:19, Catonano wrote:
> If I do
> 
> $ guix environment --ad-hoc guix guile
> 
> $ guile
> 
>> (use-modules (guix http-client))
> 
> it's ok.
> 
> If I do
> 
> $ guix environment --ad-hoc guix guile-next ;; <-- note the "-next"
> 
> $ guile
>> (use-modules (guix http-client))
> 
> Then there is no code for module http-client
> 
> Is there any hope that I can load some guix modules from within a
> guile-next prompt ?
> 
> I'm asking this because I am exploring Culturia and that requires
> guile-next.
> 
> I'd like to use the guix http-client and the Culturia machinery
> together

IIRC guix on guile-next is in the work, in the mean time you can use
the http.scm module from culturia [0] which relies on curl command line.
There is even a chime for http-get which works with https.

Be aware that I've hit some issues with that procedure, I'm not sure
but I think under some condition it leaks memory...

Don't hesitate to ask if you hit issues.

HTH,

[0] https://github.com/amirouche/Culturia/blob/master/src/http.scm

-- 
Amirouche ~ amz3 ~ http://www.hyperdev.fr

      parent reply	other threads:[~2016-10-07 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 16:19 guix with guile-next Catonano
2016-10-07 16:31 ` Thompson, David
2016-10-07 16:47 ` Amirouche Boubekki [this message]

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=4ba270f1bf4607aa364d964b42210322@hypermove.net \
    --to=amirouche@hypermove.net \
    --cc=catonano@gmail.com \
    --cc=help-guix-bounces+amirouche=hypermove.net@gnu.org \
    --cc=help-guix@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.
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).