From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add SEEK.
Date: Tue, 28 Jun 2016 22:50:37 +0200 [thread overview]
Message-ID: <87furxf36q.fsf@mdc-berlin.de> (raw)
In-Reply-To: <877fdqb5a9.fsf@gmail.com>
Alex Kost <alezost@gmail.com> writes:
> Ricardo Wurmus (2016-06-15 16:31 +0300) wrote:
>
>> * gnu/packages/bioinformatics.scm (seek): New variable.
[…]
> Is 'fold' really needed here? What about:
>
> (every (lambda (dir)
> (with-directory-excursion (string-append "tools/" dir)
> (zero? (apply system* "make" make-flags))))
> dirs)
No, “fold” is not needed. I always forget that we have “every”. Thanks
for the reminder! I changed it and pushed to master.
~~ Ricardo
prev parent reply other threads:[~2016-06-28 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 13:31 [PATCH] gnu: Add SEEK Ricardo Wurmus
2016-06-15 13:31 ` Ricardo Wurmus
2016-06-15 19:50 ` Alex Kost
2016-06-28 20:50 ` Ricardo Wurmus [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=87furxf36q.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=alezost@gmail.com \
--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).