From: Leo Famulari <leo@famulari.name>
To: Ben Woodcroft <donttrustben@gmail.com>
Cc: Guix-devel@gnu.org
Subject: Re: [PATCH 3/3] gnu: Add khmer.
Date: Fri, 17 Jun 2016 03:23:58 -0400 [thread overview]
Message-ID: <20160617072358.GA3618@jasmine> (raw)
In-Reply-To: <1466126601-30932-4-git-send-email-donttrustben@gmail.com>
On Fri, Jun 17, 2016 at 11:23:21AM +1000, Ben Woodcroft wrote:
> + (build-system python-build-system)
> + (arguments
> + `(#:phases
> + (modify-phases %standard-phases
> + (add-after 'unpack 'set-paths
This phase deletes bundled libraries and then copies one of the
libraries back in from another package (murmur-hash).
Can khmer refer to murmur-hash without it being bundled at all?
> + (lambda* (#:key inputs outputs #:allow-other-keys)
> + ;; Delete bundled libraries.
> + (delete-file-recursively "third-party/zlib")
> + (delete-file-recursively "third-party/bzip2")
> + ;; Replace bundled seqan.
> + (let* ((seqan-all "third-party/seqan")
> + (seqan-include (string-append
> + seqan-all "/core/include/seqan")))
> + (delete-file-recursively seqan-all)
> + (mkdir-p seqan-include)
> + (rmdir seqan-include)
Here it makes the directory seqan-include and then removes it. Should it
be reversed? Would it be simpler to delete the directory and then use
copy-recursively, which I don't think requires mkdir-p?
> + (copy-file (string-append (assoc-ref inputs "seqan")
> + "/include/seqan")
> + seqan-include))
> + ;; Replace bundled MurmurHash.
> + (let ((smhasher "third-party/smhasher/"))
> + (delete-file-recursively smhasher)
> + (mkdir smhasher)
> + (for-each
> + (lambda (file)
> + (copy-file
> + (string-append
> + (assoc-ref inputs "murmur-hash") "/include/" file)
> + (string-append smhasher file)))
> + (list "MurmurHash3.cpp" "MurmurHash3.h"))
> + (rename-file
> + (string-append smhasher "MurmurHash3.cpp")
> + (string-append smhasher "MurmurHash3.cc")))
> + (setenv "CC" "gcc")
I think this variable setting should be in its own phase.
next prev parent reply other threads:[~2016-06-17 7:24 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 [this message]
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
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=20160617072358.GA3618@jasmine \
--to=leo@famulari.name \
--cc=Guix-devel@gnu.org \
--cc=donttrustben@gmail.com \
/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).