From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add libBigWig.
Date: Thu, 25 Feb 2016 11:37:38 +0100 [thread overview]
Message-ID: <idja8mp2hzh.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20160225014702.GE31607@jasmine>
Leo Famulari <leo@famulari.name> writes:
> On Wed, Feb 24, 2016 at 05:21:47PM +0100, Ricardo Wurmus wrote:
>> Hi Guix,
>>
>> the description is a little short. Basically, this is a cleaner
>> reimplementation of a popular tool/library that is released under a
>> non-commercial license. There is little more I can say about it and the
>> original description just references that other tool.
>>
>> Any ideas how to improve this?
>
> If you think it will be clear to the intended audience, I'd say it's
> fine.
Okay.
> If "Kent's library" is well-known in the field, would it make sense to
> refer to it?
I don’t know. They refer to the kentUtils, but I don’t really want to
mention them. They are a grab bag with many different features (only
one of which is reading bigwig files), so I don’t think it would clarify
much.
>> + (add-before 'install 'create-target-dirs
>> + (lambda* (#:key outputs #:allow-other-keys)
>> + (let ((out (assoc-ref outputs "out")))
>> + (mkdir-p (string-append out "/lib"))
>> + (mkdir-p (string-append out "/include"))
>> + #t))))))
>
> Does it make sense to upstream this? I understand if it's not worth your
> time...
Done:
https://github.com/dpryan79/libBigWig/issues/6
A new commit has already been made but there’s no release with that
change yet. I’ll add a comment to this phase.
Thanks for taking the time to review this patch!
~~ Ricardo
next prev parent reply other threads:[~2016-02-25 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 16:21 [PATCH] gnu: Add libBigWig Ricardo Wurmus
2016-02-25 1:47 ` Leo Famulari
2016-02-25 10:37 ` Ricardo Wurmus [this message]
2016-02-25 19:38 ` 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=idja8mp2hzh.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.