all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add eschalot.
Date: Tue, 30 Aug 2016 03:11:32 -0400	[thread overview]
Message-ID: <20160830071132.GD4193@jasmine> (raw)
In-Reply-To: <87eg5blecv.fsf@we.make.ritual.n0.is>

On Fri, Aug 26, 2016 at 03:49:36PM +0000, ng0 wrote:
> TL;DR: only run the test suite if you own a cluster, super computer or
> otherwise much computation power which will be bored by this
> hashing. Everyone else will spend MANY hours on this, which is why make
> check/test is disabled.

How many is MANY? ;)

> +;; There is no release candidate but commits point out a version number.
> +(define-public eschalot
> +  (let ((commit "0bf31d88a11898c19b1ed25ddd2aff7b35dbac44")
> +        (revision "1"))
> +    (package
> +      (name "eschalot")
> +      (version (string-append "1.2.0-" revision "." (string-take commit 7)))
> +               (url "https://github.com/schnabear/eschalot")

I think this is okay.

> +      ;; Licenses are various as eschalots cites the applications it was based on
> +      ;; or which it was influenced by, eschalot author says the application itself
> +      ;; is under a BSD license, the combination of all could be seen as expat or
> +      ;; a variation of such.  It is not clear.  FIXME: Specify license(s) used.
> +      (license (license:non-copyleft
> +                "file://LICENSE"
> +                "See LICENSE in the distribution for the licenses which apply.")))))

It uses the ISC license and the Expat license.

  reply	other threads:[~2016-08-30  7:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 15:49 [PATCH] gnu: Add eschalot ng0
2016-08-30  7:11 ` Leo Famulari [this message]
2016-08-30 11:01   ` ng0
2016-08-30 11:09   ` ng0
2016-08-30 17:34     ` Eric Bavier
2016-08-30 18:45       ` ng0
2016-09-06 21:22         ` Leo Famulari

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=20160830071132.GD4193@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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.