unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: flexbar: Enable tests.
Date: Mon, 27 Apr 2015 14:37:34 +0200	[thread overview]
Message-ID: <idjsibleohd.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87a8xt96to.fsf@fsf.org>


David Thompson writes:

> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>
>> this patch enables the tests of flexbar.  There is no check target but a
>> validation script and some test data, so I'm just running the script
>> instead of "make check".
>
> Looks fine to me!  Minor critique below:

Thanks.

>>         #:phases
>> -       (alist-delete 'install %standard-phases)))
>> +       (alist-replace
>> +        'check
>> +        (lambda* (#:key outputs #:allow-other-keys)
>> +          (setenv "PATH" (string-append
>> +                          (assoc-ref outputs "out") "/bin:"
>> +                          (getenv "PATH")))
>> +          (chdir "../flexbar_v2.5_src/test")
>> +          (zero? (system* "bash" "flexbar_validate.sh")))
>> +        (alist-delete 'install %standard-phases))))
>
> Consider rewriting using 'modify-phases' syntax.

I think in this particular case, using "modify-phases" wouldn't be much
clearer.  Here we're just deleting one and replacing another phase and I
think it's as clear as things can be.  Or is the use of "alist-*" in
package definitions deprecated?

(I should rewrite my icedtea7 patch, however, to use "modify-phases"
syntax.  With so many custom phases it really makes sense.)

~~ Ricardo

      reply	other threads:[~2015-04-27 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  9:49 [PATCH] gnu: flexbar: Enable tests Ricardo Wurmus
2015-04-27 10:57 ` David Thompson
2015-04-27 12:37   ` 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=idjsibleohd.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=dthompson2@worcester.edu \
    --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).