unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix build side - including modules (guix hash), (guix gcrypt): How to provide shared library?
Date: Mon, 02 Jan 2017 23:03:34 +0100	[thread overview]
Message-ID: <87y3yt86h5.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_imk+krS6heOTjHU5j4spjTPyQZE7zq0VRwvTQLgaH4OFfQ@mail.gmail.com> (David Craven's message of "Mon, 2 Jan 2017 15:31:31 +0100")

David Craven <david@craven.ch> skribis:

>> Also, why is sha256 used via FFI via an external library? It's not exactly difficult to implement in Guile :P
>
> I'm not sure we want to write our own crypto primitives... And it's
> not quite as trivial, I don't know or care what a Newton-Raphson
> algorithm is ;)
> http://stackoverflow.com/questions/24093199/a-pure-scheme-implementation-r5rs-of-sha256

I suspect it would be slow with Guile 2.0, and (guix hash) is used in
performance-critical locations.

That said, if there’s a need for it on the build side where performance
does not matter much, it makes sense to add a pure-Scheme
implementation.  I think Weinhölt’s Industria library has one.

Alternately, we could make it easier to import (guix hash).  All we need
is to create a custom (guix config) module where ‘%libgcrypt’ is found
to the right thing, or something like that.

HTH!

Ludo’.

      reply	other threads:[~2017-01-02 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02  2:16 Guix build side - including modules (guix hash), (guix gcrypt): How to provide shared library? Danny Milosavljevic
2017-01-02 10:06 ` David Craven
2017-01-02 13:51   ` Danny Milosavljevic
2017-01-02 14:31     ` David Craven
2017-01-02 22:03       ` Ludovic Courtès [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=87y3yt86h5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=david@craven.ch \
    --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 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).