unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: Guix-devel@gnu.org
Subject: Re: [PATCH] Add khmer.
Date: Fri, 17 Jun 2016 13:54:31 -0400	[thread overview]
Message-ID: <20160617175431.GA9008@jasmine> (raw)
In-Reply-To: <5763C61C.1050402@uq.edu.au>

On Fri, Jun 17, 2016 at 07:42:52PM +1000, Ben Woodcroft wrote:
> Hey Leo, thanks for the thoughts.
> 
> On 17/06/16 18:16, Leo Famulari wrote:
> > On Fri, Jun 17, 2016 at 11:23:18AM +1000, Ben Woodcroft wrote:
> > > 'murmur-hash' takes the code from a repository SMHasher, but I'm not
> > > interested in packaging that. That is OK?
> > I'll try packaging SMHasher. Hopefully it's not too hard.
> 
> Go right ahead if you like. However, I wouldn't really recommend it because
> the only function of it is to test the quality of different hash algorithms,
> which probably isn't useful as anything except as an end in itself, and in
> that case a user might want to manage the compilation flags themselves
> anyway. But I won't stand in your way, of course.

I saw that SMHasher was just a test suite for hash algorithms [0], but I
don't really have any idea how it would be used in practice. So, perhaps
you're right that every user would have their own set of flags they want
to build with, making our package less useful.

> What if we change the name of the package to 'smhasher' and leave packaging
> the binary for later if someone is really interested?

Is murmur designed to be bundled? If there are no proper releases of a
library, then does it make sense to roll-our-own packaging like this?

[0] But also the reference implementation of murmur and potentially some
other algorithms?

  reply	other threads:[~2016-06-17 17:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  1:23 [PATCH] Add khmer Ben Woodcroft
2016-06-17  1:23 ` [PATCH 1/3] gnu: Add python-screed Ben Woodcroft
2016-06-17  2:07   ` Leo Famulari
2016-06-17 22:57     ` Ben Woodcroft
2016-06-17  1:23 ` [PATCH 2/3] gnu: Add murmur-hash Ben Woodcroft
2016-06-17  1:23 ` [PATCH 3/3] gnu: Add khmer Ben Woodcroft
2016-06-17  7:23   ` Leo Famulari
2016-06-17 23:41     ` Ben Woodcroft
2016-06-25 17:30       ` Leo Famulari
2016-06-17  8:16 ` [PATCH] " Leo Famulari
2016-06-17  9:42   ` Ben Woodcroft
2016-06-17 17:54     ` Leo Famulari [this message]
2016-06-25 17:29 ` Leo Famulari
2016-06-26  9:58   ` Ludovic Courtès
2016-06-26 11:59     ` Ben Woodcroft
2016-06-26 17:34       ` Leo Famulari
2016-06-26 22:48         ` Ben Woodcroft
2016-06-27  5:01           ` Leo Famulari
2016-06-27  5:47             ` Ben Woodcroft

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=20160617175431.GA9008@jasmine \
    --to=leo@famulari.name \
    --cc=Guix-devel@gnu.org \
    --cc=b.woodcroft@uq.edu.au \
    /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).