unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add bedtools
Date: Sat, 13 Dec 2014 00:00:28 +0100	[thread overview]
Message-ID: <87zjaspj77.fsf@gnu.org> (raw)
In-Reply-To: <idj388lkwih.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Fri, 12 Dec 2014 11:11:50 +0100")

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> Since there is no install phase in the Makefile I had to write a
> replacement to copy all tools from the build bin/ directory to the
> output /bin/ directory.  I don't know if it is better to explicitly list
> the tools to copy or if this should rather be done with a glob pattern.

Is a glob pattern really needed, or is it that bin/* must be copied?

If the latter, you could use ‘scandir’ to obtain the list of files in
that directory, or (find-files "build/bin" ".*") where the 2nd argument
is a regexp, not a glob pattern.

> Another source of ugliness in the recipe is the
> patch-makefile-SHELL-definition phase which is really just
> patch-makefile-SHELL but working on ":=" definitions rather than
> "=" assignments.  Augmenting patch-makefile-SHELL to handle definitions
> as well would result in a cleaner package recipe.

Yeah; let’s fix that in core-updates.

> +       (alist-cons-after
> +        'unpack 'patch-makefile-SHELL-definition
> +                (lambda _

Please align ‘(lambda’ with ‘'unpack’.

> +                  (define (find-shell name)
> +                    (let ((shell
> +                           (search-path (search-path-as-string->list (getenv "PATH"))
> +                                        name)))
> +                      (unless shell
> +                        (format (current-error-port)
> +                                "patch-makefile-SHELL: warning: no binary for shell `~a' found in $PATH~%"
> +                                name))
> +                      shell))

‘find-shell’ is not needed: just use the procedure called ‘which’.

Could you send an updated patch?

Thanks,
Ludo’.

  reply	other threads:[~2014-12-12 23:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 10:11 [PATCH] gnu: Add bedtools Ricardo Wurmus
2014-12-12 23:00 ` Ludovic Courtès [this message]
2014-12-13  6:42 ` Mark H Weaver
2014-12-15 15:46   ` Ricardo Wurmus
2014-12-16 17:18     ` Ludovic Courtès
     [not found] <20141215155541.GA19757@jocasta.intra>
     [not found] ` <idj61db7vu0.fsf@bimsb-sys02.mdc-berlin.net>
2014-12-16 10:15   ` John Darrington

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=87zjaspj77.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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).